Jonothan Farr writes:
oid = object._p_oid
Is this unique for the interpretor session? Or is this oid constant for that object and stroed in the FileStorage?
Yes, yes, and yes.
I'm not sure how to answer the rest of your questions...
But they're so simple? Not.
You could implement a storage object that did anything you wanted on the back end. Keep in mind that when you store an object, you only know essentially the oid, the timestamp of the transaction, and a pickle of the data you're storing. You could in theory unpickle the data and use some mechanism for determining where you want to store it. Problem is when you load an object, you only know the oid, so you need some other mechanism of determining where to load the object from based on oid alone. Also, as Jim has mentioned, handling undo and versions with multiple storages is a 'tricky' problem. ;)
--jfarr
I'm curious, does a transaction in the FileStorage contain all the oid's to be effected by that transaction? Is it split-up (appended) by transaction or oid? Transaction, I believe. All my best, Jason Spisak CIO HireTechs.com 6151 West Century Boulevard Suite 900 Los Angeles, CA 90045 P. 310.665.3444 F. 310.665.3544 Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.