#34437: values() doesn't mention annotations as valid choices on resolving error
-------------------------------------+-------------------------------------
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: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):
In [changeset:"dce1b9c2de00a3385c029c02dca325f44e7697a4" dce1b9c]:
{{{#!CommitTicketReference repository=""
revision="dce1b9c2de00a3385c029c02dca325f44e7697a4"
Fixed #36480 -- Made values() resolving error mention unselected aliases.
Follow-up to cb13792938f2c887134eb6b5164d89f8d8f9f1bd. Refs #34437.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34437#comment:3>
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 visit
https://groups.google.com/d/msgid/django-updates/01070199716c755f-aba2730c-e3a0-4823-8443-603a301c84f1-000000%40eu-central-1.amazonses.com.