#26610: Case insensitive indexes
-------------------------------------+-------------------------------------
Reporter: shadow7412 | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: index charfield | Triage Stage: Accepted
textfield case insensitive |
optimisation |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by shadow7412):
I've done some reading on {{{citext}}} - and it would indeed do the job I
want it to do.
My only concern is that iexact effectively becomes implicit, which may
surprise some developers.
I guess the question is: would people value being able to do both
insensitive and sensitive searches on the same field?
The only other way I could think to do this would be creating a functional
index, which would give the ability to have the different index kwargs as
I had in the original report, but I'm not sure which wins from a
performance point of view.
And, again, if people would find having both a useful feature.
--
Ticket URL: <https://code.djangoproject.com/ticket/26610#comment:5>
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/068.f6bfdd02951d56901d2caccfa642eb11%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
