-
Notifications
You must be signed in to change notification settings - Fork 118
South 0016 Migration MySQL #129
Comments
I'm able to reproduce this issue using MySQL 5.6.22. OP reported he was using 5.6.17 here. OP is running Django 1.6.x and Python 2.7.9. |
Tested some more with MySQL query logging on. I've taken part of the log that seems to be migration 0016. What I see is that the entire migration is completed, but then the constraint is added again which gives the error and a rollback. I've tested with MySQL 5.6.23 and 5.5.41, both seem to have the same problems. I use Django 1.6, South 1.0.2 and MySQL-python 1.2.5. |
I've now tried it with and without using |
|
@Nalanae are you able to run the tests in the aldryn-newsblog package?
|
When I run the tests against SQLite or MySQL they run fine. However, when I check a MySQL query log of just the testrun, I can't find any mention of the problematic constraints. I'll investigate further into the log. If you want to have a look into the log: https://dl.dropboxusercontent.com/u/6635899/mysql.log.zip |
When I change the call to djangocms-helper to use migrations I can force the error.
|
Should be fixed by #132 |
Migration is now working on mysql db.
Changed row 17 and 21 to if connection.vendor not in ['sqlite', 'mysql', ]:
error message:
FATAL ERROR - The following SQL query failed: ALTER TABLE
aldryn_newsblog_latestentriesplugin
ADD CONSTRAINTapp_config_id_refs_id_522159a1
FOREIGN KEY (app_config_id
) REFERENCESaldryn_newsblog_newsblogconfig
(id
);The text was updated successfully, but these errors were encountered: