Home » Search

About dirty

51-60 of 74Refresh
Issue
2

Use temporary files to enable very large transactions

" />                 <dirty-tracking arrays="true" />         dirty entities after flush
Forum
1

Connection is closed Caused by: java.io.EOFException

" level2="0" /> <dirty
Forum
1

Degrading performance overtime

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

Different behavior with persist() and queried instances?

doesn't mark the object dirty when getting changed so a following merge call doesn't bring any success
Forum
1

First query takes 4+ minutes to complete

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

Insertion Speed Rate and Batch Load

always="auto" on-persist="false" on-commit="true" />   <dirty-tracking arrays="false" />
Issue
1

javax.servlet.ServletException: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getPropertyName

. No problem. Build 2.2.6_01 included a dirty and quick fix that used get as a prefix for both get and set
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