#32690: Q object __or__ appears to get all dunder related's default columns and
queryset raises ProgrammingError.
-------------------------------------+-------------------------------------
Reporter: allen-munsch | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(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
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"e3bde71676a704e27d62e5f96dd967f7305db7f2" e3bde716]:
{{{
#!CommitTicketReference repository=""
revision="e3bde71676a704e27d62e5f96dd967f7305db7f2"
Refs #32690 -- Altered lookups Query rhs alterations during
initialization.
Having it happen at the lookup creation time ensures entry points
called before the compilation phase (e.g. get_group_by_cols) don't have
to duplicate the logic in charge of altering Query instances used as
rhs.
It also has the nice effect of reducing the amount of time the
alteration logic to once as opposed to multiple times if the queryset
is compiled more than once.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32690#comment:15>
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/070.dd6d501591f30e819f20d7910eeb2c4f%40djangoproject.com.