#27151: FK index created two times on PostgreSQL if referenced table PK is
varchar
----------------------------------+------------------------------------
Reporter: Kamil Kujawiński | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.8
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by Kamil Kujawiński):
Replying to [comment:6 Markus Holtermann]:
> Exactly what Maciej Gol said. VARCHAR fields with an `db_index=True`
have 2 indexes. One for exact matches, one for LIKE.
Agree.
I thought that those are same indexes with only different name. My pg
query doesn't show any differences between them. I found in Django code
that `_like` index is created with `varchar_pattern_ops` option.
So problem is with my pg query, not with Django.
Sorry for bother.
--
Ticket URL: <https://code.djangoproject.com/ticket/27151#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.dd2ea0f229e202e8b65994570379e874%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
