my only suggestion that I don't see in the wiki is to create a backup version of the table(s) before you attempt any DDL transactions. you could then you the 'insert INTO .. select ...' syntax to do your conversions. that way you keep all your old data if/when u screw up. this should be OK for most small-medium size tables.. and if you are doing large ones you should be doing your own custom SQL anyways.
On 2/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Jacob Kaplan-Moss wrote: > > Hey folks -- > > > > I've posted (over 1200 words of) my thoughts on schema evolution to the > > wiki: http://code.djangoproject.com/wiki/SchemaEvolution. > > > > Any thoughts before I start on this? > > > > Jacob > > I'm not sure exactly what reparations you're thinking will be possible > by rolling back a DDL transaction. I'm pretty sure most db's don't > have full transaction control over DDL. Issuing a DDL statement > usually involves at least an implicit commit, so, e.g., if something > goes wrong three DDL commands into your evolution you're not going to > be able to roll back to initial state. Backing up the db before the > series of DDL statements is only sure way to guarantee a rollback for > all db's, I think. > > -- Herb > > > > -- [EMAIL PROTECTED] -- blog: http://feh.holsman.net/ -- PH: ++61-3-9877-0909 If everything seems under control, you're not going fast enough. - Mario Andretti --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
