Comment 7 for bug 907878

Revision history for this message
Adam Gandelman (gandelman-a) wrote :

Well, I believe at this point in the migrations, all mysql tables are innodb as they are converted in an earlier migration 022_set_engine_mysql_innodb.py. The issue seems to only trigger when mysql is configured as innodb prior to the initial migrations (which is the default now in Ubuntu as of Precise). The commit that this reverts appears to go about in a better way than the hack before, in that it attempts to manually find the correct FK to drop instead of relying on sqlalchemy to resolve it automatically (which apparently it cannot do in the case where InnoDB was used from the get-go)