ObjectDB Database Search

101-118 of 118 results


	NullPointerException while setting a new property value ); } else { em. merge (o); } } em.getTransaction().commit(); } finally { if (em.getTransaction
	Best practice: Database update/migration of embedded databases in products - for renaming packages, classes and fields. The scenario in your post, of merging and splitting
	Help understanding Entity behavior with JPA entity of that ID by using find or merge . Non managed objects with the same ID may be replaced by
	Suspected memleak caused by bad state of EntityManager the InternalException, the EntityManager throws every time when doing merge operation, but it can be closed
	Foreign key constraint issue (cascade = {CascadeType. MERGE , CascadeType.REMOVE}, mappedBy = "parent", orphanRemoval = true)
	Lazy loading does not work - crud takes long . for(Datapoint d: list){ em.remove(em. merge (d))} fjubuu Maik The class definitions including
	Storing a tree of data (depth=3) ; /** real name of person in life. */ @NonNull @ManyToOne(cascade = CascadeType. MERGE ) private Performer
	persists and update together ? BASOL Maybe merge instead of persist is what you are looking for. support Support
	Master database switching to read-only mode, possibly caused by slave failure . merge (EMImpl.java:456) at sun.reflect.GeneratedMethodAccessor528.invoke(Unknown Source) at sun
	a second mapping-file is ignored in persistence.xml by enhancer .EMImpl. merge (EMImpl.java:520) Best regards, BTC-ES btc_es BTC EmbeddedSystems Please check
	How to move @Embedable collection to a dedicated entity class? , e.g. by merging many small objects into fewer large objects, it could improve performance. maybe
	Feature Request for database.obj$ file I've two questions and maybe feature requests regarding the $file. a) is there a valid method to check when everything is done after closing the database? background : As far as we recognized there is a background thread, merging the database.obj and the database.obj§ files. As long as this daemon
	Multiple joins did not return expected result Running two different separate queries and merging the results (e.g. into a Java set, maybe
	ObjectDB 2.6.3 Maven repository and Maven examples to work with TomEE . Fixed handling merge of an entity with PK == 0 ( issue #1667 ).
	2.9.x query issue with @Unique constraint (for LEFT OUTER JOIN). [Step 4] Merge the results of steps 2, 3 using OR. [Step 5] Apply selection
	com.objectdb.o.InternalException: java.lang.ArrayIndexOutOfBoundsException: null: IllegalArgumentException($error); } boolean ok = owner.addOwnedElement(ownedElement); // if (ok) { // em. merge (owner
	ObjectDB 2.4.4 fields in queries. Fixed a regression bug of duplicating new objects on merge . Fixed a Doctor bug that caused false alarms.
	ObjectDB 2.4.6 Fixed a regression problem of version 2.4.5 in running in GlassFish. Fixed a bug in retrieving primary key fields in queries (on index merging ). Fixed a bug in using a collection field index in queries. Fixed query plan selection for queries with boolean indexed field. Fixed a NullPointerException