#25752: RenameField on m2m causes error when new m2m field is added with old
name
-------------------------------------+-------------------------------------
Reporter: skyjur | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: postgres migrations | Triage Stage:
renamefield | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by skyjur):
The workaround I used was to rename those sql indexes with additional
RunSQL:
{{{
migrations.RunSQL(
'alter table cms_test_many_2e06cda4 rename to
cms_test_many_legacy_2e06cda4',
'alter table cms_test_many__legacy_2e06cda4 rename to
cms_test_many_2e06cda4'
)
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25752#comment:4>
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.a4cf8f34de8ceeab6570d0beb17bc839%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
