Django - migrating only new migrations after loading dump

Asked Oct 19 '20 at 07:08

Active Oct 19 '20 at 07:49

Viewed 259 times

The migration process of my test suite got very long in my project, so I created a pg_dump which I load to my DB each time I run my unit tests.

Now the pg_dump was created manually, (which later I tend to integrate into a CI system) However now, I have some other migrations I created after the dump (and I don't want to create a new dump) and I need to run migrations.

My question: How do I make django migrate only the new migrations? When running python manage.py migrate it migrates everything, it migrates all the migrations as if the dump was not loaded

I searched for this topic online but found addressing this specific problem. The closest thing I found was this post which wasn't very helpful for me Django backup strategy with dumpdata and migrations

EDIT: This happened because I didn't load the dump the test database, after fixing that it worked,

edited Oct 19 '20 at 07:49

asked Oct 19 '20 at 07:08

MyCoolAwsomeName

What do you mean by "everything"? If you load the **pg_dump** before you run `manage.py migrate`, django will only apply new migrations. – Lord Elrond Oct 19 '20 at 07:12
it migrates all the migrations as if the dump was not loaded – MyCoolAwsomeName Oct 19 '20 at 07:16
1

Does your **pg_dump** include the `django_migrations` table? – Lord Elrond Oct 19 '20 at 07:18
It then isn't loaded otherwise the first migration will fail already. Are you sure you're loading your dump into the *test* database? – Oct 19 '20 at 07:18
@Melvyn you are correct, I didn't load the dump to the test database thanks! – MyCoolAwsomeName Oct 19 '20 at 07:48

Django - migrating only new migrations after loading dump

0 Answers0