#26551: Django ORM generates invalid PostgreSQL query with Inverted Q() object 
that
crosses relations
-------------------------------------+-------------------------------------
     Reporter:  Erik B. Andersen     |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  1.9
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  fixed
     Keywords:  Q(), postgreSQL      |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"e124d2da94cc1233729d8f0200809589f6c5afc8" e124d2d]:
 {{{
 #!CommitTicketReference repository=""
 revision="e124d2da94cc1233729d8f0200809589f6c5afc8"
 Fixed #26551 -- Fixed negated Q() queries that span relations.

 Prevented queries from reusing trimmed joins.
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/26551#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 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.37f16776f3e2722dd6ad37dc87cfc1c8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to