 5 | that were deleted, specifically not including the number of dependent and embedded instances. Dirty |
5 | are unchanged and the instances revert to transient. Additionally, dirty instances transition |
5 | 2.0 int DIRTY Since: JDO 2.0 int LOAD Since: JDO 2.0 int STORE Since: JDO 2.0 |
3 | " level2="0" />
<dirty-tracking arrays="false" /> My persisted class, "JdoBlob2", only contains a byte ... jdoPreStore(){
// A dirty object, via setData(), strongly references byte[] via "data" field, so ignore ... doesn't hold strong references to entity objects unless necessary (e.g. for dirty objects until commit |
2 | , makes them dirty and persists them. Check that new embedded objects are created and then delete ... , made them dirty and persisted them. So far everything went smooth, the new embedded objects were created |
2 | " on-commit="true" />
<dirty-tracking arrays="false" />
<dirty |
2 | - but the difference is that when using enhancement - an entity doesn't become dirty just by changing ... order to fix orphan removal). If Customer is not dirty - it doesn't cascade persisting |
2 | :05:23 #188 *]
transaction Id = 506009, new file size = 297009152, dirty pages = 1, update list
s = 2, dirty page map = 1, Thank you for this report. It indicates an unexpected ObjectDB state |
2 | " on-commit = "true"/>
<dirty-tracking arrays = "true"/>
Changed settings ... "/>
<dirty-tracking arrays |
2 | "/>
<dirty-tracking arrays ... the issue of dirty tracking of arrays. However, I have these new concerns: 1) why does objectdb |