#25317: Altering a 1to1 field to FK on Postgres drops uniqueness but does not
create index
-------------------------------+------------------------------------
Reporter: synotna | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Changes (by shaib):
* cc: shaib (added)
* status: closed => new
* resolution: invalid =>
* stage: Unreviewed => Accepted
Comment:
Ok, I see now. The PG backend relies on the unique constraint to create an
index (correctly) for a 1-1 field; which means, if the field is no longer
unique but still a FK, it needs an explicit index.
(you can probably work around this by adding a single-field
`index_together` entry to your Meta)
--
Ticket URL: <https://code.djangoproject.com/ticket/25317#comment:5>
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.b717ee896105c09f179f606483d2d0d5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
