ObjectDB Database Search

51-60 of 60 results


	Transaction isolation support? a different update of that specific object using the first EntityManager , due the default optimistic
	Updating Entities ._OptimisticLockException: Optimistic lock failed for object application.model.Paygrade#184 (object
	Replication error on slave restart this on slave after step 3: com.objectdb.o.UserException: Optimistic lock failed (see multiple nested
	Criteria query error: Unexpected query token ) @GeneratedValue private Long id; /** * Version of object, supporting optimistic lock */ @Column (name = "opt
	Remove not working .PersistenceManagerFactoryClass", "com.objectdb.jdo.PMF"); properties.setProperty("javax.jdo.option. Optimistic ", "true
	Remove an entity which attributes were changed We use an OSGi environment and we have three OSGi plugins. In plugin A an entity is loaded and the entity is passed to plugin B. Plugin B changes an attribute on the entity. Plugin C removes the entity from the database. After commit the transaction an exception is caused with optimistic
	ObjectDB 2.7.6 lock free Synchronization ( issue #2327 ). Fixed a regression optimistic lock exception bug
	Removed entities can be found by query in the same transaction . It solves another issue (unexpected optimistic lock exception) but you may want to check if it also solves this issue. support Support
	ObjectDB 2.1.0 Added Online Backup utility ( issue #16 ). Added Master-Slave Replication / Clustering (issue #17 ). Added a PDF version of the ObjectDB manual (included in the download). Added sample (tutorials) Maven projects (included in the download). Added support of disabling optimistic locking
	Entity Version History ObjectDB manages automatic entity versioning (for optimistic lock purposes). Every entity object modification is reflected by a new version number. Naturally, previous values in the entity object that are overridden by new values are discarded. Some applications may benefit from the ability