FAQ: https://docs.djangoproject.com/en/dev/faq/install/#what-are-...
> you’ll also need a database engine. PostgreSQL is recommended, because we’re PostgreSQL fans
geoDjango (bundled): https://docs.djangoproject.com/en/dev/ref/contrib/gis/instal...
> PostGIS is recommended
the migration document also clearly notes that postgres has the best migration support, although it does not outright recommend it (probably because migration is generally an afterthought and production database has already been decided by then)
So I think it's also South who's not as good in doing upgrades in MySQL as it is with PostgreSQL
https://wiki.postgresql.org/wiki/Transactional_DDL_in_Postgr...
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
https://docs.djangoproject.com/en/dev/ref/databases/
I've only used Django with SQLite but I would be shocked if it was actively recommending a single database. It would imply that somehow Django doesn't work as well with the others.