#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
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"1a13161eab2d040990734f80b3eedea354f6a4ba" 1a13161]:
{{{
#!CommitTicketReference repository=""
revision="1a13161eab2d040990734f80b3eedea354f6a4ba"
Refs #33766 -- Removed unused Join.equals().
It's unused now that the specialized FilteredRelation.as_sql logic is
no more.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33766#comment:18>
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/01070187b231bc6d-90cc76be-825e-40e5-b080-936d90baab4c-000000%40eu-central-1.amazonses.com.