Hi Adam,
All of your suggestions are perfectly valid things to do (and are in fact
things I've done in the past). This particular project uses data migrations
fairly heavily, and the developers haven't been particularly good about
making sure they run cleanly on fresh databases. We are using Dj
Do you have an example? If you're using Django's default testing framework,
it normally creates a fresh database, so from the moment a new data
migration is written it would be tested with the empty database scenario.
Afaiu it is possible to write RunPython operations in a way that no-ops on
empty
