ObjectDB Database Search

51-61 of 61 results


	Optimistic lock failed pessimistic exceptions, but it is more efficient to remain with optimistic locking (which is the default
	Some technical questions ? Yes, if it has not been locked with pessimistic WRITE. , and will it see the old attribute? Yes
	Where Does ObjectDB Block/Lock? a queue) you will need multiple PersistenceManager instances. In ObjectDB 1.x pessimistic locks
	ObjectDB 2.6.8 Added JPA XML validation schema files to Maven/JEE objectdb.jar. Added automatic release of pessimistic locks on client-server connection failure. Fixed an OptimisticLockException bug on commit after flushing a removed modified entity object. Fixed a NullPointerExeption on new index building
	NPE at com.objectdb.jpa.JpaQuery.getResultList O'Hare It seems as a separate issue. Maybe related to pessimistic locking. Can you provide a test
	ObjectDB 2.3.2 instead of Long ) and then updated. Fixed retrieval with pessimistic lock to bypass cache and to force refresh.
	ObjectDB 2.3.1 UnsupportedOperationException error message. Fixed a pessimistic lock timeout bug ( issue #520 ). Fixed
	InternalException during producer/consumer scenario and LockMode set to PESSIMISTIC _WRITE. This results in the exceptions below. Could you advise on the errors
	ObjectDB 2.2.1 Added support for using ObjectDB with JBoss AS 6.0 / 6.1 . Fixed several bugs in handling eager fetch. Fixed a pessimistic locking bug . Fixed a bug in using primary key fields in queries. Fixed a bug in queries on deleted objects before commit / flush.
	ObjectDB 2 JDO Manual however, married to JDO, although I think it's good. Its lack of true (before commit) pessimistic locking
	ObjectDB 2.8.5 Fixed a bug in using AS in SELECT NEW (breaks some Spring Data JPA queries). Fixed a bug in tracking changes to new collections after flush ( issue #2640 ). Fixed a StackOverflowError on no access permission to objectdb.conf ( issue #2643 ). Fixed a bug in managing pessimistic locks after using