#24096: GROUP BY on oracle fails with TextField and BinaryField
-------------------------------------+-------------------------------------
     Reporter:  jarshwah             |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  master
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by shaib):

 The meta option is indeed attractive. I would add a twist: Allow a field
 to declare itself deferred (this would somewhat parallel), that is, a new
 field option `deferred=False`.

 Build into that some API which will let the LOB field find out that
 they're on Oracle (or, more generally, a backend with
 `can_compare_lobs=False`), and you also get the automatic-compatibility.

--
Ticket URL: <https://code.djangoproject.com/ticket/24096#comment:8>
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/066.d2662532e03247b82adc06175f9a4297%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to