#11580: Unable to query TextField against oracle nclob 10Gr4
-------------------------------------+-------------------------------------
Reporter: nosrednakram | Owner: shaib
Type: Bug | Status: assigned
Component: Database layer | Version: 1.6
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: oracle TextField | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by shaib):
Partial [https://github.com/django/django/pull/3544 PR] fixes the
`contains` lookup, up for review of the method of installing backend-
specific custom lookups.
Note that the code uses DBMS_LOB.INSTR -- the preferable way to do this is
using CONTAINS, but that requires the text-field to be indexed.
Just removing the DBMS_LOB.SUBSTR as suggested works with the LIKE
queries, but breaks the exact ones.
--
Ticket URL: <https://code.djangoproject.com/ticket/11580#comment:12>
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/070.cd4696f83152a63c983629b950e8d519%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
