#24082: Unique=True on TextField or CharField should not create an index
-------------------------------------+-------------------------------------
Reporter: djbug | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.7
(models, ORM) |
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
-------------------------------------+-------------------------------------
Comment (by shaib):
Replying to [comment:7 djbug]:
>
> A single `text_pattern_ops` index works for '''both''' `LIKE` & `=`
queries. But it won't work for other operators like `< <= etc.`. But, I
feel that, it would be an overkill to create 2 indexes by default. It
should be left to the user to decide if they want double index or a single
one with whichever operator class they want.
I disagree; it is much easier to notice a superfluous index, or an
explicitly-removed one (once `db_index=False` works), than one that is
partly-missing (will work for anything except LIKE). If you're at the
point where a superfluous index is hurting your performance, you're likely
to be paying much closer attention to your database anyway; a missing
index will hurt you much earlier.
--
Ticket URL: <https://code.djangoproject.com/ticket/24082#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/063.81910bf62d9fc0e8cd70c839a9418ea5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
