4 ms·
South does complain every time a MySQL migration has problems and you get recommended to use Postgres there. Other than that I haven't noticed any preference in
by collyw 13y ago
South does complain every time a MySQL migration has problems and you get recommended to use Postgres there. Other than that I haven't noticed any preference in the Django documentation in 3 years.
- raverbashing 13y agoYes, but it complains less with some upgrades (I've seen it happen) So I think it's also South who's not as good in doing upgrades in MySQL as it is with PostgreSQL
- jeltz 13y agoNot a Django guy but my guess is that it has nothing to do with South and all to do with that PostgreSQL supports transactional DDL while MySQL does not.
- raverbashing 13y agoTrue, however transactional DDL doesn't seem to be a problem after MySQL 5.5 https://wiki.postgresql.org/wiki/Transactional_DDL_in_PostgreSQL:_A_Competitive_Analysis#MySQL https://wiki.postgresql.org/wiki/Transactional_DDL_in_Postgr...
- masklinn 13y agoThis only demonstrates that rollbacking an insertion after creating a table within a transaction now works. That is, it shows DDL does not completely break a transaction it's performed in. According to the documentation DDL remains non-transactional in MySQL 5.5[0] > The CREATE TABLE statement in InnoDB is processed as a single transaction. This means that a ROLLBACK from the user does not undo CREATE TABLE statements the user made during that transaction. [0] http://dev.mysql.com/doc/refman/5.5/en/implicit-commit.html http://dev.mysql.com/doc/refman/5.5/en/implicit-commit.html