Re: Object Oriented Storage
Date: October 12, 2005 10:25PM
I've thought about this several times but the problem I keep coming back around to is the cost of the serializing of the data. To me this is a bit of a killer and even though you could do an "Object Cache" the initial cost is quite high.
What I have considered is the following:
1) Customer storage engine that runs a JVM/bytecode/whatever so that objects can be played with as objects.
2) Serialize the objects into a blob store as the first step.
3) Generate the schema from object store... aka auto extend the schema from encapsulation points. This is tricky but can be done today.
4) Always have a "object" field so that you can retrieve the object. Wrap the client API so that you can take this field and de-serialize on the client side.
5) Create a "object-cache" so that you can keep objects open in the table so that they can be accessed as needed in a native manner.
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.