ObjectDB ObjectDB

Internal Website Search

31-40 of 151 resultsRefresh
26

EM close causes an exception

This stack trace indicates a missing temporary file that holds information about uncommitted flushed ... . It was added to support large flush operations. Since this is a hidden feature, no similar reports from ... ) will add better support for large flush operations. However, we cannot provide information regarding
3

javax.persistence.EntityExistsException

is invoked, or the EntityExistsException or another PersistenceException may be thrown at flush or commit
3

persist(entity)

at flush or commit time.) IllegalArgumentException - if the instance is not an entity
3

javax.persistence.LockTimeoutException

not result in transaction rollback. This exception may be thrown as part of an API call, at, flush or
3

javax.persistence.OptimisticLockException

. This exception may be thrown as part of an API call, a flush or at commit time. The current transaction
3

clear()

Method javax.persistence.EntityManager void clear() Clear the persistence context, causing all managed entities to become detached. Changes made to entities that have not been flushed to the database will not be persisted. Since: JPA 1.0
3

Removed entities can be found by query in the same transaction

__odbtracker/m (type STA, value=Persistent-Deleted-Flushed) which shows that the entity is deleted and flushed. The bug was introduced with ObjectDB Version 2.7.4_04, therefore in the moment ... the database and the change was flushed but not committed yet then the database maintains
0

javax.jdo.annotations.Unique

javax.jdo.annotations Annotation Unique Target: Classes and fields (including property get methods) Annotation for a database unique constraint. Used for database schema generation to create unique constraints. Also used to reorder database operations when flushing changes to avoid unique
0

makePersistent(pc)

, then flush or checkConsistency should be called after attaching the instances. These methods have no effect
0

javax.jdo.Query

instances of affected classes in the cache are first flushed to the datastore. Instances in the cache or

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support