#35744: Combine query support doesn't repoint nested external references
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"53ea4cce2fd08e84b9cdb6363267ccb9525f7060" 53ea4cce]:
{{{#!CommitTicketReference repository=""
revision="53ea4cce2fd08e84b9cdb6363267ccb9525f7060"
Fixed #35744 -- Relabelled external aliases of combined queries.
Just like normal queries, combined queries' outer references might fully
resolve before their reference is assigned its final alias.
Refs #29338.
Thanks Antony_K for the report and example, and thanks Mariusz Felisiak
for the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35744#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/010701928d568ccf-e00488ea-ae86-48af-ae4a-0eec7a0031a9-000000%40eu-central-1.amazonses.com.
