Recreation of foreign key constraints when changing type of referenced primary key

gregorjerse · March 15, 2022, 10:54am

I have a question regarding Django version 3.2.12.

When I change the DEFAULT_AUTO_FIELD to BigAutoField and create&apply migrations, the foreign keys of auto-generated through tables are dropped. This can be observed by running sqlmigrate which drops foreign key relations but never recreates them.

I noticed this is already fixed in Django 4.0.3 (Refs #32743 -- Fixed recreation of foreign key constraints when alter… · django/django@3d9040a · GitHub) but not in 3.2.x branch.

Can I expect this commit will in time be applied to Django 3.2.x branch? I would like to migrate to BigAutoField to be future-proof, but would prefer not to write migrations by hand.

Topic		Replies	Views
ticket 34151 investigation and help needed for next steps Mentorship	2	192	March 9, 2023
Django is using primary keys ints and foreign keys bigint. How do I solve this? Using the ORM	4	769	April 1, 2023
Django migration creating copy tables Using Django	4	1263	December 2, 2020
Django Unit Tests Raising Duplicate Key Constraint Errors on object Creation Using the ORM	3	2513	April 20, 2022
Django doesn't automatically remove the uniqueness constraint from the database when changing it in a subsequent migration? Using the ORM	3	268	February 17, 2024

Recreation of foreign key constraints when changing type of referenced primary key

Related Topics