On Aug 20, 2013, at 9:06 PM, Clifford Yapp wrote: > I think that sounds good - so to "downgrade" the attributes it would > be something like "attr upgrade -v3" ? Part of me wonders if that > would set up an expectation for dbupgrade supporting a similar > capability...
Something like that. I don't think the same implementation is easily doable with the database format, but it is possible. At least, it'd be nowhere nearly as simple as it should be with attributes. I have thought a bit about forgoing the attr-specific version altogether. Instead, we could just let the database version be incremented with every little backwards-incompatible change we might want to make. You can think of this as v6, v7, v8 or even simply as a v6 that is designed with upgradability built into it (e.g., with a minor revision number) starting right where we're at now with v5. Basically, it mostly requires command infrastructure so that upgrading is trivial and pervasive. Not a lot of work, but it would have to be incredibly robust and safe. That's obviously simultaneously very appealing and potentially catastrophic for obvious reasons. Cheers! Sean ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
