From: Michael P. <mp...@pl...> - 2008-02-27 22:05:13
|
Noam Weinstein wrote: > In your vision, would these methods be called after the element > definition has changed? If so, how will the defunct elements be made > available to the callback function (won't thawing the story throw an > error if the data doesn't match the new definition?) If not, how will > the data be ported to the new fields? Yeah, that's sort of a chicken-egg problem. In the past we've fixed this by "deprecating" an element. Basically just marking it hidden and if it is in its own package, moving that package into a /deprecated directory/namespace. So the first upgrade that removes an element would have to deprecate it and the next one would be free to remove it entirely. Can you think of ways to improve this? I really don't want to have to deal with lots of deprecated elements lying around just taking up space :) -- Michael Peters Plus Three, LP |