On 2010-11-06 14.13, Niclas Hedhman wrote:
Not sure what you are really saying. Is it that something loops the
entire entity store, modifies every entry and not commit that until
all are done??
Because purely reading all the entity states should result in
everything residing in memory, would it?
Correct. Big database -> OutOfMemoryException.
The solution below is potentially very slow, basically doing a
"commit" on each, right? Where most systems get much better
performance on batch operations.
Perhaps this mail is moot, after the I/O addition of Backup/Restore
functionality...
It is. I have implemented a variant using the Input/Output that saves
100 migrated entities at a time, so much faster.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
