Repository format changes are only part of the problem. Whenever somebody changes the schema for Chandler, your repository needs to be re-created.
This is because we don't support schema evolution, yet.
I could add support for repository format evolution which is much much simpler to implement than schema evolution but given that it's only part of the story, it wouldn't buy us much for the amount of work involved because schema evolution would still be missing.
Andi..
On Fri, 6 May 2005, Jared Rhine wrote:
Does the Chandler roadmap include a release at which repository migration (between repository versions) will be supported? (Automatically or via external scripts?)
I have no particular feelings on the matter. Delaying migration support is good to allow more time to nail the repository format. If people start to actually use 0.6 dogfood-style, then data migration will be helpful, maybe even expected despite any documented warnings. Linux distro packagers will want to know how this is handled in the 0.7 timeframe because they generally code in support for upgrades into their packages. Migration doesn't have to be easy, pre-1.0, but it should be possible.
I'd guess it's either a 0.6, 0.6.1, or 0.7 feature.
PS. This all occurred to me because I got a python traceback from 0x5000 to 0x5200 instead of the popup I got from previous upgrades.
-- [EMAIL PROTECTED]
"We suffer primarily not from our vices or our weaknesses, but from our illusions. We are haunted, not by reality, but by those images we have put in place of reality." - Daniel J. Boorstin _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
