]> git.ipfire.org Git - thirdparty/patchwork.git/commit
migrations: don't go to the db for 0041_python3 migration
authorDaniel Axtens <dja@axtens.net>
Fri, 16 Jul 2021 17:19:37 +0000 (03:19 +1000)
committerStephen Finucane <stephen@that.guru>
Thu, 12 Aug 2021 16:47:20 +0000 (17:47 +0100)
commit3a979ed8bfc69aecb38e3a8280e87996c5384482
tree7a558c2f8d38ce08812f353c8f409f48f25bdbce
parent0c1e208ce96205cfe3d3fcf27c87c11da71d7442
migrations: don't go to the db for 0041_python3 migration

When we moved to Python 3, makemigrations wanted to change a bunch of
things, see commit 4ad87ed72aec ("migrations: Add the Python 3 patch").

The change is, as observed then, just to make django happy; it's not
supposed to change the database at all.

So make the migration change the state as seen by Django only.
This makes the migration ~instant, even for a huge database.

Signed-off-by: Daniel Axtens <dja@axtens.net>
Reviewed-by: Stephen Finucane <stephen@that.guru>
Related: #420
patchwork/migrations/0041_python3.py