#33766: FilteredRelation resolves its conditions too late which can result in
unknown alias references at SQL compilation time
-------------------------------------+-------------------------------------
Reporter: Daniel Schaffer | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: filteredrelation | Triage Stage: Ready for
coalesce | checkin
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
Comment:
In [changeset:"d660cee5bc68b597503c2a16f3d9928d52f93fb4" d660cee5]:
{{{
#!CommitTicketReference repository=""
revision="d660cee5bc68b597503c2a16f3d9928d52f93fb4"
Fixed #33766 -- Resolved FilteredRelation.condition at referencing time.
The previous implementation resolved condition at Join compilation time
which required introducing a specialized expression resolving mode to
alter the join reuse logic solely during that phase.
FilteredRelation.condition is now resolved when the relation is first
referenced which maintains the existing behavior while allowing the
removal of the specialized resolving mode and address an issue where
conditions couldn't spawn new joins.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33766#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070187b231bc35-1a61a3f3-bad4-4d95-891a-e1a8b45f85b1-000000%40eu-central-1.amazonses.com.
