Sqlmigrate generated SQL

[andrea crotti]

Related to this other thread:

https://groups.google.com/forum/#!msg/django-users/V8Ei2qZJ8VI/bFUeY2wTAQAJ;context-place=forum/django-users

I'm working on trying to find a workaround for migrations killing our local/CI servers, until there is a better fix in Django stable..

So started this project to do some analysis:

https://github.com/AndreaCrotti/django-migrations-analysis

One interesting thing is that it looks like using sqlmigrate (taking some code from it) to generate the raw SQL and composing ti basically generates exactly the same final schema for the database.

https://github.com/AndreaCrotti/django-migrations-analysis/blob/master/commands/sqlmigrate_all.py

In general the question is, assuming all the settings are the same, can they differ under some conditions?

I guess for example that using RunPython would cause issues in this case right?

[andrea crotti]

Answering to myself obviously sqlmigrate can't really do anything with code in RunPython.

So I suspect the biggest problem would be something like this:

- early data migration that uses an initial schema a certain model

- a later schema migration that changes that

so trying to generate the SQL after would not apply because the schema changed in the meanwhile..