#25317: Altering a field to ForeignKey does not create index
-------------------------------+--------------------------------------
Reporter: synotna | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 1.8
Severity: Normal | Resolution: invalid
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 timgraham):
My understanding is that an index
[https://docs.djangoproject.com/en/1.8/ref/models/fields/#unique shouldn't
be created] in this case since `OneToOneField` is `unique=True`: "Note
that when `unique` is `True`, you don’t need to specify `db_index`,
because `unique` implies the creation of an index."
--
Ticket URL: <https://code.djangoproject.com/ticket/25317#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/065.aebefbdc6cab599e1a73b112ae8a45fe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
