On 2013-08-01, at 11:23 , Nigel Legg wrote: > So are you saying the migration wil or will not work with South using > MySQL??
No. I'm saying if the migration fails the database will be left in an intermediate (and likely incorrect) state. > What do I have to do, in addition to everything in the South > documentation, in orde3r to make a South migration work with MySQL, given > what you have posted above? South *works* with mysql. But because of *mysql's limitations* if there is a problem while South is *modifying the database schema* (the DDL) it has no way to *rollback the changes*. That's what it tells you: if there is a a problem during the migration (because there's a bug in your migration), south *can not* put the database back in the state it was before you started the migration because mysql *does not provide the tools to do so*. It's not an incompatibility, it's mysql being a gigantic turd, no migration tool can fix that no matter how much they polish it. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
