Re: [Django] #3575: postgres backend should optimize iexact searches
Django
-------------------------------------+-------------------------------------
Reporter: Jack Moffitt | Owner: jacob
<metajack@…> | Status: new
Type: | Version: master
Cleanup/optimization | Resolution:
Component: Database layer | Triage Stage: Accepted
(models, ORM) | Needs documentation: 0
Severity: Normal | Patch needs improvement: 1
Keywords: | UI/UX: 0
Has patch: 1 |
Needs tests: 1 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by shmishleniy@…):
* status: closed => new
* severity: => Normal
* type: => Cleanup/optimization
* easy: => 0
* ui_ux: => 0
* resolution: fixed =>
Comment:
Hi!
Not so far good to provide "out the box" solution to replace ILIKE on
UPPER or LOWER.
You guys forced us to override standard backends.
The are so many cases when the best solution is use ILIKE.
Two pic to quick example on small TEST db:
1. Using UPPER
[[Image(http://s23.postimg.org/9qatun20b/upper.png)]]
2. Using ILIKE
[[Image(http://s22.postimg.org/vdq1d3q75/ilike.png)]]
Yes of course we can create UPPER index but it's too expensive to have
UPPER and norml case indexes.
--
Ticket URL: <https://code.djangoproject.com/ticket/3575#comment:27>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: Jack Moffitt | Owner: jacob
Type: | Version: master
Cleanup/optimization | Resolution: fixed
Component: Database layer | Triage Stage: Accepted
(models, ORM) | Needs documentation: 0
Severity: Normal | Patch needs improvement: 1
Keywords: | UI/UX: 0
Has patch: 1 |
Needs tests: 1 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
* status: new => closed
* resolution: => fixed
Comment:
Please don't reopen tickets that have been closed for 5 years. If you wish
to suggest an improvement, please open a new ticket. You can mention this
ticket in the description of that ticket. Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/3575#comment:28>