ObjectDB Database Search

Would it make sense to call entityManager. merge (o) for each of the objects returned to get the child

().clear(); em. merge (tmpDoc); // This is fine as well but should get the collection back from the DB

you men. Sorry for the stupid question. All I needed to do is a em. merge (company) once added the user to the company to attach it again... elnll002 Facundo Curti

to null. When saving the entity, I'm using merge and flush. The entity object is managed, so I think

, cascade = { CascadeType.PERSIST, CascadeType. MERGE , CascadeType.REFRESH })   private ParentEntity

? Regarding the merge errors, did you start getting them only after fixing the database? According

Our application has some complex entities. We do batch update( merge detached entity) every 2 minutes. We find the period significant IO costs these days, and disappeared when turn off the batch updating. 1.ObjectDB is in embedded mode. 2.ObjectDB version is 2.3.7 3.Database file size is nearly

adding class by class into that one, it seems that they ODB didn't merge all classes, as it does if I

expected when you call persist . It is unclear what methods in JPA the JpaRepository uses. Maybe merge

. merge (EMImpl.java:514) at models.core.db.objectdb.ObjectDBBaseModel.update(ObjectDBBaseModel.java:75

.getTransaction().begin(); em. merge (guest); em.getTransaction().commit(); em.flush(); em.clear(); em.close

an instance managed and persistent.", and unlike merge () there is no managed entity returned. My copious

). You may create a copy of that object (maybe by JPA's  detach + merge or by JDO's detachCopy

Hi, I have a question about package name and searching for entities. As for now we were using two different databases for two different parts of our system. But we want to make a 'common' model for both systems. After merging entities from two different projects, we get single jar

on new features continuously, but for the sake of stability they will not be merged into

); } else { em. merge (o); } } em.getTransaction().commit(); } finally { if (em.getTransaction

- for renaming packages, classes and fields. The scenario in your post, of merging and splitting

entity of that ID by using find or merge . Non managed objects with the same ID may be replaced by

Fixed Java Agent / Java EE / Spring enhancement bug. Fixed a bug in merging detached entity objects. Fixed unexpected  NullPointerException in client server mode. Fixed an exception in AVG query on non numeric values ( issue #107 ). Fixed a bug in handling JOIN queries with primary key fields.

Added support for using ObjectDB with JBoss AS 7.1.1. Improved performance of merging managed entities. Fixed a deadlock . Changed license checks.

Changed merge behavior (following this forum thread ).  Fixed a TomEE - ObjectDB client-server integration issue ( issue #1407 ). Fixed a ClassCastException on selecting an embedded ID field in queries. Fixed an exception ( NullPointerException ) in update queries (since 2.5.5_12). Fixed

object. Fixed merging entity objects of another EntityManager . Fixed a bug in concurrent

a NullPointerException is merging objects of new types . Fixed a bug in managing inverse (mapped by) collections and maps in reflection mode.

)')). [Step 1d] Order the results of step 1c by:   v$1. [Step 1e] Merge the results of steps 1b

How do you get the duplicate primary key error? Are you using persist ? You may try merge instead

parameters display in the Explorer schema window. Fixed merging a new entity object with application set primary key.

.productVariantOid='1344763'). [Step 3] Merge the results of steps 1, 2 using OR. [Step 4] Filter the results

.main(RemoteTestRunner.java:197) wua Andreas Wurm Thank you for your report. It will be merged

it again, things go crazy during commit and merging !??   quasado Alexander Adam Hmm getting closer

Fixed bugs in cascading merge and refresh. Fixed an internal  java.lang.ArrayStoreException bug (com.objectdb.o.InvToOneLoadRequest). Fixed a regression bug (starting 2.4.4_13) in handling embeddable types. Fixed a performance regression (since 2.4.4_01) in query result retrieval. Added INFO

bugs in using flush. Fixed bugs in cascading merge . Fixed a multithreading deadlock bug . Fixed a bug

Fixed a bug of  duplicating new objects during merge . Fixed a username/password issue in using EntityManagerFactory 's getMetamodel . Fixed a bug in detachment of hollow objects on close ( issue #799 ). Fixed a Doctor exception ( issue #796 ). Fixed a Doctor bug in checking byte[] arrays

with the object Db Documentation: http://www.objectdb.com/java/jpa/entity/id Unfortunately, while merging

When stopping my JEE 6 Web Profile application in Glassfish 3.1.1, I sometimes get this exception, yielding in not merging athene.odb and athene.odb$. A bug in objectdb?    bjjl@ps2:~$ ls -l /var/db/athene/ total 122080 -rw-r--r-- 1 bjjl webservd   2621440 2012-05-24 16:40

Maven repository and Maven examples to work with TomEE . Fixed handling merge of an entity with PK == 0 ( issue #1667 ).

(for LEFT OUTER JOIN). [Step 4] Merge the results of steps 2, 3 using OR. [Step 5] Apply selection