[DGD] another aspect of persistence

[chris .]

I've come across another aspect of persistence i need to consider in my overall design.  I made up a function to update libs and objects.  One of the first things i noticed, since I was using set_long(x) in create() for an objects long desc, than upgrading does nothing to reflect a change to the description (since the object was already created).
To get around this, I've thought about calling an upgrade function in each object getting upgraded which works similar to create (for values which don't change over time).  In addition i have figured on using something like set_long(long() )...or else just have query_long return long().
I've shot down several other ideas i came up with to solve this...in fact every solution so far seems to have some drawbacks or in the least quite a bit of extra work.
Im going to hit the drawing board soon, and try to come up with a better option than the one i just mentioned.  Im particularly concerned that my approach is a real OLC-based design killer (requiring values to ultimately be determined by a function instead of a variable).
I wondered how else members of this community dealt with this.
Thanks all,
-chris
_________________________________________________________________
Stay up to date on your PC, the Web, and your mobile phone with Windows Live.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/