#28803: When renaming foreign key indexes don't get renamed which breaks next
migrations
-------------------------------+--------------------------------------
Reporter: Jacek Bzdak | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Jacek Bzdak):
Workaround for this issue is, to add two Alter field migratons (before and
after rename), one takes down the index other recreates it --- if you have
large dataset probably you should just rename the index manually.
--
Ticket URL: <https://code.djangoproject.com/ticket/28803#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.6869d0ae80eb40ea460ddf2e7d164e4c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
