On 17 March 2012 10:53, Kevin Meyer - KMZ <[email protected]> wrote: > > One thing, though - as much as possible, please don't break database > history, unless you have to - I have an app that uses the current > database layout/values, and would prefer to not *have* to lock it to > 0.2.0-incubating. But I will if that is what is required. >
I suspect that the SQL object store will have the smallest number of issues - at the end of the day the data is in tables, all that is changing is the in-memory representation. Where there could be bigger issues is with the xml object store and the nosql object store, because there we take generate a string representation of the Oid and write out to disk. But thinking it through, I suspect we could write some reasonably simple code that would understand these "legacy" on-disk formats and do an update on-the-fly as they need to. Let me know if you think of anything else I should be aware of, though. Cheers Dan > > Regards, > Kevin > > >
