#33159: Missing table alias in generated query after used in subquery
-------------------------------------+-------------------------------------
     Reporter:  Michal Čihař         |                    Owner:  Mariusz
                                     |  Felisiak
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  4.0
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):

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


Comment:

 In [changeset:"903aaa35e5ceaa33bfc9b19b7f6da65ce5a91dd4" 903aaa3]:
 {{{
 #!CommitTicketReference repository=""
 revision="903aaa35e5ceaa33bfc9b19b7f6da65ce5a91dd4"
 Fixed #33159 -- Reverted "Fixed #32970 -- Changed WhereNode.clone() to
 create a shallow copy of children."

 This reverts commit e441847ecae99dd1ccd0d9ce76dbcff51afa863c.

 A shallow copy is not enough because querysets can be reused and
 evaluated in nested nodes, which shouldn't mutate JOIN aliases.

 Thanks Michal Čihař for the report.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33159#comment:4>
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/063.73eec5fc2a535307b356ead379352415%40djangoproject.com.

Reply via email to