Hi Craig > Slow getting through my email backlog after vacation...
I hope you enjoyed it;-) > The explicit evict methods are intended for this kind of memory > management usage. Are there issues with evict for your purposes? The scenario in which I use it, is when creating a large tree-like structure of objects. Once I have a part of this tree created, I doesn't needs to be accessed anymore, so all fields could be cleared (including strong references), in which case all the nodes in the tree can be garbage collected. So I would like to be able to do something like this: after creating so many nodes flush the intermediate results to the datastore and clean up memory, but if something fails the complete creation of the tree should be cancelled. The evict doesn't help out in this scenario: "...If evictAll with no parameters is called, then all persistent-clean instances are evicted (they transition to hollow)..." In the described scenario the already processed nodes are persistent-dirty so they won't become hollow. kind regards, Christiaan -- View this message in context: http://www.nabble.com/Spec%3A-retainValues-%2B-flush%28%29-tf4297510.html#a12383253 Sent from the JDO - User mailing list archive at Nabble.com.
