Niclas Hedhman wrote: > On Mon, Aug 25, 2008 at 7:03 AM, Rickard Öberg <[EMAIL PROTECTED]> wrote: >> Hey, >> >> While doing research on another topic I found this little gem on data >> formats and migration: >> http://blog.omnigroup.com/2007/09/17/omnifocus-what-weve-learned-so-far-engineering/ >> >> I think we could reasonably easily follow the approach they describe for >> how to detect changes in schemas and then update to new formats etc. in >> a generic non-store-specific way. > > I am not sure what in that blog that is catching your eye.
The way they deal with what happens when the schema changes and broken databases, i.e. keep the transaction list and reapply. This would be useful for server-server synchronization as well. > If it is > that the data store is built from a journal of changes, then I can say > that perhaps it is possible and perhaps even nice, but it is > definitely not enough. Structural changes bigger than adding and > removing a field is common. Yup, agree. But it's a good start. /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
