[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Upgrading ozone applications
If i understand you correctly you are creating and storing objects during
one cycle and then in the next cycle redesigning the classes so that data is
held differently and the composition and inheritance structure changes but
you want to move the data from the old design to the new. AFAIK there is
currently no automagic support for this. You will have to write a conversion
program that takes you from one state to the other. If you have any ideas
how this could be automagically done by the server please let us know.
Schema evolution has been on the TODO list for a while.
----- Original Message -----
From: "Lasse Lindgård" <firstname.lastname@example.org>
Sent: Saturday, May 26, 2001 3:22 PM
Subject: Upgrading ozone applications
> I have been looking at the ozone-db. It looks very interesting.
> I have one big problem though:
> I have a flying fast development team working og our serverside
> That leaves us little or no time to map our object structure to old
> relational databases. All we need is an object storage.
> We are working on a long-term project (a standard CMS product). So we
> just settle for a DB-structure and tweak our objects. We want full freedom
> to refactor.
> If I use a relational database, I would know how to write SQL scripts that
> can upgrade data from one model to another. I have been there, done that
> (and it sucks).
> How would I solve this problem if I was using Ozone for storing my data ??