#26034: Altering CharFields to have both db_index=True and unique=True crashes
on
postgresql
-------------------------------------+-------------------------------------
Reporter: kaedroho | Owner: timgraham
Type: Bug | Status: closed
Component: Migrations | Version: 1.8
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"3d324b9614afa1e9b391b30f6f21d2f65fa8ac90" 3d324b9]:
{{{
#!CommitTicketReference repository=""
revision="3d324b9614afa1e9b391b30f6f21d2f65fa8ac90"
[1.9.x] Fixed #26034 -- Fixed incorrect index handling on PostgreSQL on
Char/TextField with unique=True and db_index=True.
Thanks Simon Charette for review.
Backport of 56aaae58a746eb39d5e92ba60f59f4c750a8e1a8 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26034#comment:9>
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.08f7f6563dbc24e2f17e714cba004acc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
