wiki:BackwardsIncompatableChanges
Last modified 5 years ago Last modified on 06/12/09 21:40:13

0.6

  • The ORM instance passed to the backwards() method now uses the models from the previous migration (or no models if that migration is the first). This should not affect many users; however, if you have combined a data and schema migration, look out.

0.5

  • South now exists in the south/ subdirectory, rather than the root, of SVN checkouts and downloadable packages. Please make sure your import paths are correctly updated.

0.4

  • The post_syncdb signal is now send at the end of the migration set rather than as soon as the table is made. This may cause problems if your code relies on the table being an older schema than it is currently; however, we believe it fixes a lot more problems than it creates.