#23794: FieldDoesNotExist error in migration with deleted fields and
unique_together constraint
-------------------------------------+-------------------------------------
Reporter: heybuddy | Owner: trg
Type: Bug | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: fixed
Keywords: migration | Triage Stage: Accepted
unique_together removefield | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"feded19104b14bc28aaccf550265157df84593ba"]:
{{{
#!CommitTicketReference repository=""
revision="feded19104b14bc28aaccf550265157df84593ba"
[1.7.x] Fixed #23794 -- Fixed migrations crash when removing a field
that's part of index/unique_together.
Backport of 72729f844e0dd9bd01b3874171b89ab0d136a40e from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23794#comment:7>
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/066.9311ebe033e7442767031aae38aa0bc3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
