#26090: Changing a ForeignKey to a OneToOne field leaves an extraneous index
behind
----------------------------+------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.9
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"9356f63a99957f01c14a9788617428a172a29fcb" 9356f63a]:
{{{
#!CommitTicketReference repository=""
revision="9356f63a99957f01c14a9788617428a172a29fcb"
Fixed #25317, #26090 -- Fixed swapping combinations of unique and db_index
during migrations.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26090#comment:3>
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/067.3d1151369b56ade87477063d938bce4b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
