About dirty

61-70 of 80Refresh
Forum
1

locks on pure query activities

serialization="false" /> <dirty
Forum
1

Need to close+open database for a commit to be taken into account

Hi, I have one case where commit (update of entity in this case) is not taken in account unless database is actually closed and re-open, no error. I tried to use flush instead of close+re-open but it does not work. So currently there is a dirty close + open + reload on each update
Issue
1

New entity objects are duplicated on merge cascading

managed ..." exception, when the duplicated object is referenced from another new / dirty entity
Forum
1

Occasionally slow requests in load testing

" /> <dirty-tracking arrays="false
Forum
1

Out of memory

" /> <dirty-tracking arrays="false" /> This big heap space is set
Forum
1

OutofMemory error with Object DB 2.0

" /> <dirty-tracking
Forum
1

Performance tuning, best practices

" on-persist="false" on-commit="true" />   <dirty-tracking arrays="true" />
Forum
1

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
Forum
1

Replication Issue

" on-persist="false" on-commit="true" />                 <dirty-tracking arrays="false
Forum
1

Schema migration - long to String

and write (after making them dirty) all the instances of that modified type immediately after the change