| [CDO] intermediate save for swapping [message #686865] |
Wed, 11 May 2011 09:06 |
 John Smith
Messages: 137
Registered: July 2009 |
Senior Member |
|
|
Has anybody experiences with models which are build by some algorithm,
getting a size of several gigs, and storing them in a database? I wonder
if one could save the CDOResource in some time intervals while the
algorithm is running, so that the CDOObjects get into the CLEAN state
and can be CDO-garbage-collected, which is not possible for NEW
CDOObjects I guess, is my understanding correct?
The algorithm is designed in a way that it produces no dangling
references at any stage (i.e. each cross-referenced object is contained
in the CDOResource at any time). This should be a good starting point
for my plan of above, right? Anything else to consider?
A further step would be to load a very large XMI file incrementally into
a CDO database. Suitable stages to save the model while reading the XMI
file are maybe at stages where all forward-references are resolved (the
XMI loader I thing resolves all references at the end, but this behavior
can be changed with a little programming I think). Or maybe just saving
the model continuously while reading, and also at the end when all
references get resolved. The XMI resource loader has the
no-dangling-reference property I think (assuming the unresolved
references are not present as proxies but are managed separately and
resolved at the end, not sure about this point).
What are your opinions on this topic?
|
|
|
Powered by
FUDForum. Page generated in 0.03101 seconds
] 
Search
Help
Register
Login
Home
