django-migrations

I have a production database and need to keep safe the data. I want to change a Field in model and convert all data inside that database with this change. Old field class MyModel(models.Model): field_name = models.TimeField() Changed field class MyModel(models.Model): field_name = models.PositiveIntegerField() Basically I want to convert the TimeField value (that has a Time object) in minutes. Example: I have in an object time(hour=2, minute=0, second=0) and I want to convert that field value in all database table to 120 when I apply the migrate. Safest way that I always do is: create another

I can't find reference to particular issue in docs or online. I have an existing many to many relation. class Books(models.Model): name = models.CharField(max_length=100) class Authors(models.Model): name = models.CharField(max_length=100) books = models.ManyToManyField(Books) This has migrations and data. Now I need to use through option in order to add one extra field in table holding many to many relation. class Authorship(models.Model): book = models.ForeignKey(Books) author = models.ForeignKey(Authors) ordering = models.PositiveIntegerField(default=1) class Authors(models.Model): name =

I am aware of the cursor object in Django. Is there any other preferred way to execute raw SQL in migrations? I want to introduce postgresql partitioning for one of my models tables. The partition logic is a bunch of functions and triggers that have to be added to the database on setup which I'd like to automate. One way: The best way I found to do this is using RunSQL: Migrations contains the RunSQL class. To do this: ./manage.py makemigrations --empty myApp edit the created migrations file to include: operations = [ migrations.RunSQL('RAW SQL CODE') ] As Nathaniel Knight mentioned, RunSQL

In Django's migrations code, there's a squashmigrations command which: "Squashes the migrations for app_label up to and including migration_name down into fewer migrations, if possible." So, if you want to squash, say, the first 5 migrations, this will help. What's the best way to squash starting with a particular migration_name ? In a project I'm currently working on, we've added 5-10 new migration files as we've added new features. We'll deploy the whole project at once and it looks like running these individually will take too long. I'd like to squash all the migrations for this project