On Dec 12, 2:32 am, "kerinin" <[EMAIL PROTECTED]> wrote: > Anything that has been changed could be specified in the migrate file, > so for example if Class.property1 had been renamed to Class.property2, > you could specify something like this in the migrate file: > > new.Class.property2 = old.Class.property1
Why not just assume the LHS is old and the RHS is the new? Class.property1 = Class.property2 > Ideally, "tg-admin migrate" would provide a set of conversion functions > allowing you to do thing such as change MultipleJoins to RelatedJoins, > or FloatCol's to IntCols - something like this: > > new.Class.property1 = MultipleJoinToRelatedJoin( old.Class.property1 ) > new.Class.property2 = FloatColToIntCol( old.Class.property2, > round='down' ) Couldn't you just introspect this info from the old/new class and convert automatically? Other than that, makes a lot of sense, although Jorge's point about not dropping the DB is a good one. wavydavy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
