#26889: Index creation different if SlugField in CreateModel or in AddField of a
migration on postgresql
-------------------------------------+-------------------------------------
Reporter: aRkadeFR | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.9
Severity: Normal | Resolution: fixed
Keywords: migrations, index, | Triage Stage: Ready for
postgresql, slugfield db-indexes | 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:"8edfdddbc8d6a4e39c4bf175075822ca3751b054" 8edfdddb]:
{{{
#!CommitTicketReference repository=""
revision="8edfdddbc8d6a4e39c4bf175075822ca3751b054"
[1.8.x] Fixed #26889 -- Fixed missing PostgreSQL index in
SchemaEditor.add_field().
Backport of 2e4cfcd2b9a0984ad6c4087a5deebbf33413835c from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26889#comment:7>
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.2f624dbf5f7a84c48cb1c7bb0643a165%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
