So the idea is a django orm database migration system that:

  • Is simple.
  • Doesn't make you use sql. This is an orm, we shouldn't have to use sql.
  • Can be automatic. Predicts the migration script for you so you don't have to think about what has changed.
  • Works well in a version control system, or even distributed ones. Because damnit.
  • During the migration process, allows you to use the state of your previous models as if they were still there. This is key, and is not done anywhere else, as far as I know.


Overview | Installation | Tutorial | Manager Reference

Test Status

Currently tests are passing on mysql, postgresql_psycopg2, and sqlite3.


Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.