South Unable to Do DDL Transactions Under MySQL

[ortsed]

Every time South needs to run a DDL Transaction while using a MYSQL DB (for rolling back changes and other edits), it throws an "unable to run DDL Transaction error" and suggests using a different DB.

We have been able to get around this by setting:

has_ddl_transactions = True

in the mysql.py script, as it looks like MySQL 5.1.37 does have DDL Transactions, but maybe the script needs to be split up for different versions of MySQL?

[andrew]

I'm afraid MySQL still lacks support for DDL transactions, as of version 5.5:

​http://dev.mysql.com/doc/refman/5.5/en/implicit-commit.html

If you put True there, it may appear to work, but it's probably going to fail to roll back properly if you have more than database call in that migration.