#29545: Nested OuterRef not looking on the right model for the field.
     Reporter:  Aaron Lisman         |                    Owner:  Simon
                                     |  Charette
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  master
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  fixed
     Keywords:  outerref, subquery   |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):

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


 In [changeset:"8b4a43dda702fe72c254388f1be2c0c75b7a3efc" 8b4a43d]:
 #!CommitTicketReference repository=""
 Fixed #29545 -- Fixed using filter lookups againts nested subquery

 Made sql.Where resolve lhs of its child nodes. This is necessary to
 allow filter lookups against nested subquery expressions to properly
 resolve their OuterRefs to Cols.

 Thanks Oskar Persson for the simplified test case.

Ticket URL: <https://code.djangoproject.com/ticket/29545#comment:10>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Reply via email to