Internal Website Search
51-58 of 58 resultsdrop a column from table class you will have to iterate over all the relevant objects, mark them as dirty within an active | |
PostUpdate on array changes objectdb.conf file I will revisit the issue of dirty tracking of arrays. However, I have these new | |
Remove a modified entity cause an optimistic lock exception). Can you explain the optimistic lock exception? It seems that the first level cache contains yet a dirty entity | |
Different behavior with persist() and queried instances? it becomes a regular java.util.Array again which of course doesn't mark the object dirty when getting changed | |
Schema migration - long to String change. As a workaround you can read and write (after making them dirty ) all the instances | |
Entity Management Config questions Hi, the manual states the following regarding config of Entities: http://www.objectdb.com/java/jpa/setting/entities : The element specifies settings of the two cache mechanisms for entities: The ref attribute specifies the reference type for holding non dirty entities in the persistence | |
Selective merge/cascade of detatched entity classes? Merging non dirty objects is expected to be more efficient when classes are enhanced | |
New entity objects are duplicated on merge cascading from another new / dirty entity object by a reference with cascading persist disabled. The following |