Internal Website Search

class you will have to iterate over all the relevant objects, mark them as dirty within an active

objectdb.conf file I will revisit the issue of dirty tracking of arrays. However, I have these new

). Can you explain the optimistic lock exception? It seems that the first level cache contains yet a dirty entity

it becomes a regular java.util.Array again which of course doesn't mark the object dirty when getting changed

change. As a workaround you can read and write (after making them dirty ) all the instances

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

classes? Merging non dirty objects is expected to be more efficient when classes are enhanced

from another new / dirty entity object by a reference with cascading persist disabled. The following