#32673: Nested Q() objects raises ProgrammingError on PostgreSQL and Oracle.
-------------------------------------+-------------------------------------
     Reporter:  Charles Lirsac       |                    Owner:  Simon
                                     |  Charette
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  3.0
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  fixed
     Keywords:  postgresql oracle q  |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by GitHub <noreply@…>):

 In [changeset:"0aacbdcf27b258387643b033352e99e6103abda8" 0aacbdcf]:
 {{{
 #!CommitTicketReference repository=""
 revision="0aacbdcf27b258387643b033352e99e6103abda8"
 Refs #32673 -- Fixed lookups crash when comparing against lookups on
 Oracle.

 Follow up to 170b006ce82b0ecf26dc088f832538b747ca0115.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/32673#comment:6>
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/065.0332ebca4d4b117f649665d81a47350f%40djangoproject.com.

Reply via email to