Gregor Jerše
unread,Mar 22, 2022, 6:20:41 AM3/22/22Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to django...@googlegroups.com
Hi,
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 1) 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.
Regards,
Gregor