#23605: ORM neglects to use aliases it has set up when certain multiple subqueries are used -------------------------------------+------------------------------------- Reporter: ris | Owner: nobody Type: Bug | Status: closed Component: Database layer | Version: 1.7 (models, ORM) | Resolution: fixed Severity: Normal | Triage Stage: Accepted Keywords: orm subquery alias | Needs documentation: 0 Has patch: 1 | Patch needs improvement: 1 Needs tests: 0 | UI/UX: 0 Easy pickings: 0 | -------------------------------------+------------------------------------- Changes (by Tim Graham <timograham@…>):
* status: new => closed * resolution: => fixed Comment: In [changeset:"5c481db29572a387651681b43d5d4523f96b3793"]: {{{ #!CommitTicketReference repository="" revision="5c481db29572a387651681b43d5d4523f96b3793" Fixed #23605 -- Fixed nested subquery regression Added relabeled_clone() method to sql.Query to fix the problem. It manifested itself in rare cases where at least double nested subquery's filter condition might target non-existing alias. Thanks to Trac alias ris for reporting the problem. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/23605#comment:17> 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 post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/061.768f8165cd3cf99f76338b2381ecb472%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.