#11580: Unable to query TextField against oracle nclob 10Gr4
-------------------------------------+-------------------------------------
     Reporter:  Mark Anderson        |                    Owner:  (none)
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:  oracle TextField     |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Shai Berger):

 Two points:

 Replying to [comment:16 Mariusz Felisiak]:
 > Replying to [comment:15 Mariusz Felisiak]:
 > > [https://github.com/django/django/pull/15100 PR]

 IIUC, the PR discussion seems to include a workaround (a setting that
 makes the error go away). It may be worthwhile to include it in
 [https://docs.djangoproject.com/en/3.2/ref/databases/#id14 the oracle
 notes].

 > CI confirmed that it's still an issue.

 My old [https://github.com/django/django/pull/3544 PR] includes a
 technical solution to the problem. It was put on hold all these years ago,
 because I tried to do something additional in it: Define a general way for
 database backends to override a built-in lookup, without blatant
 monkeypatching. With that, the Oracle solution was done in a way which
 would have been available to a 3rd-party database backend.

 It may or may not be worthwhile to revive that idea, but either way, we
 can also take the technical Oracle solution that's given there, and apply
 it "the old way"; I hope it still works.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/11580#comment:17>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.a5b758aaf744441d402585771870a4fc%40djangoproject.com.

Reply via email to