Menu
I'm not sure if I should keep them around or not. The main reason I'm using south at the moment is to ease development changes to the model, though I suppose it will come in handy when I'm in production. Should I be keeping my local development migrations in my Git repository?
374
Deleting migration files means losing your history. This historical info is recorded in the django_migrations table in your database. if you delete migration files, you will get dependency errors. So Don't try to lose your history by deleting your migration files.
Migrations are generated per app, and are stored in some_app/migrations . Even if you do not define migrations for your apps, there will usually be migrations that take place, since you (likely) included some apps defined by Django (and other third parties) in your INSTALLED_APPS , these have migrations as well.
migrate , which is responsible for applying and unapplying migrations. makemigrations , which is responsible for creating new migrations based on the changes you have made to your models.
This isn't a technical answer, but if you:
it might be a good idea. Why would you not?
Alternatively, you could maintain a separate branch for the South migrations.
63
Yes, you should. At some point you won't be able to do schema migration without performing additional data migrations. And those are not auto generated.
20
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
