Home » Search

About merge

71-80 of 106Refresh
Result
1

ObjectDB version 2.4.4

primary key fields in queries. Fixed a regression bug of duplicating new objects on merge. Fixed a Doctor bug that caused false alarms.
Result
1

ObjectDB version 2.4.6

Version 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
Result
1

ObjectDB version 2.4.7

Version 2.4.7 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
Result
1

ObjectDB version 2.5.6

Version 2.5.6 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
Result
1

ObjectDB version 2.6.1

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

ObjectDB version 2.6.3

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

a second mapping-file is ignored in persistence.xml by enhancer

.java:1470) at com.objectdb.jpa.EMImpl.merge(EMImpl.java:520) Best regards, BTC-ES Please check
Forum
1

Adding EntityListener Throws Unexpected Internal Exception

) at com.objectdb.o.EMR.q(EMR.java:76) at com.objectdb.jpa.EMImpl.merge(EMImpl.java:514) at models.core
Issue
1

ArrayIndexOutOfBoundsException with enhanced Entity

seems to work fine though as soon as adding it again, things go crazy during commit and merging
Forum
1

Best practice: Database update/migration of embedded databases in products

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