7 | Insertion Speed Rate and Batch Load="weak" level2="0" /> <cascade-persist always="auto" on-persist="false" on-commit="true" /> <dirty |
7 | Need to close+open database for a commit to be taken into accountHi, 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 |
7 | significant performance decrease="false" /> <cascade-persist always="auto" on-persist="false" on-commit="true" /> <dirty |
7 | OutofMemory error with Object DB 2.0" /> <dirty-tracking arrays="false" /> </entities> <schema> </schema> <server> <connection |
7 | drop a column from table you will have to iterate over all the relevant objects, mark them as dirty within an active transaction (either by |
7 | First query takes 4+ minutes to complete" on-persist="false" on-commit="true" /> <dirty-tracking arrays="false" /> </entities> <schema |
7 | config optimizing" /> <dirty-tracking arrays="true" /> </entities> <schema> </schema> <server> <connection port="6136" max="100 |
1 | database corrupt-persist always="auto" on-persist="false" on-commit="true" /> <dirty-tracking arrays="true |
1 | each 1-2 days objects on some objectdb level lock/block each other" /> <dirty-tracking arrays="true" /> </entities> <schema> </schema |
1 | Best practise loading big data to hold strong references (which prevents garbage collection) to non dirty entity objects |
