#26034: Altering CharFields to have both db_index=True and unique=True crashes
on
postgresql
-------------------------------------+-------------------------------------
Reporter: kaedroho | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Release blocker | 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 timgraham):
* severity: Normal => Release blocker
* needs_better_patch: => 0
* needs_tests: => 0
* version: 1.9 => 1.8
* needs_docs: => 0
* stage: Unreviewed => Accepted
Comment:
Docs say, "Note that when `unique` is `True`, you don’t need to specify
`db_index`, because unique implies the creation of an index." Nonetheless,
we should handle this case gracefully.
--
Ticket URL: <https://code.djangoproject.com/ticket/26034#comment:1>
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.1c71ca5370892d57e8cf5a188dfb9d6b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
