#21204: Query.defer() failure - deferred columns calculated per table instead
per
alias
-------------------------------------+-------------------------------------
Reporter: Anssi Kääriäinen | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | 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 Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"b3db6c8dcb5145f7d45eff517bcd96460475c879" b3db6c8d]:
{{{
#!CommitTicketReference repository=""
revision="b3db6c8dcb5145f7d45eff517bcd96460475c879"
Fixed #21204 -- Tracked field deferrals by field instead of models.
This ensures field deferral works properly when a model is involved
more than once in the same query with a distinct deferral mask.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/21204#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/01070182ed9c94a9-0420a842-7a79-4c17-aab0-c78ba2dbad10-000000%40eu-central-1.amazonses.com.