About dirty

71-80 of 80Refresh
Forum
1

Query results are not up to date for entities, not primitives

-persist always="auto" on-persist="false" on-commit="true" />   <dirty-tracking arrays="false
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
Forum
1

Selective merge/cascade of detatched entity

().commit(); Thanks very much, Phil Do you use enhanced classes? Merging non dirty objects
Issue
1

Best practise loading big data

(which prevents garbage collection) to non dirty entity objects. Can you share a heap dump
Forum
1

significant performance decrease

="false" /> <dirty
Forum
1

The server cannot start in CentOS

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

Unable to stop server after starting in SSL mode

" /> <dirty-tracking arrays
Forum
1

Update Entity references if we change the type of an entity

as dirty and changes will be committed. So after the database update your application can be used