#15659: Contains lookups give wrong results on SQLite3 backend
-------------------------------------+-------------------------------------
Reporter: boxm | Owner: nobody
Status: closed | Milestone: 1.3
Component: Database | Version: 1.3
layer (models, ORM) | Keywords: sqlite
Resolution: needsinfo | Has patch: 0
Triage Stage: | Needs tests: 0
Unreviewed |
Needs documentation: 0 |
Patch needs improvement: 0 |
-------------------------------------+-------------------------------------
Changes (by boxm):
* version: SVN => 1.3
Comment:
The GLOB operator is case-sensitive so could be used in place of LIKE for
contains queries - it uses unix wildcards rather than SQL ones, but that's
containable in the operators() array.
Alternatively, and probably too hard, it looks like this is fixable using
the sqlite3_create_function() to replace the definition of LIKE with one
that does the right thing (presumably including working for icontains as
well).
A minimal fix would be to document this limitations in the SQLite database
notes - at the moment the info is split between the contains/icontains
filter documentation and the SQLite db notes - which lead to me missing
it.
--
Ticket URL: <http://code.djangoproject.com/ticket/15659#comment:4>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
