#31714: ResolvedOuterRef object has no get_lookup
-------------------------------------+-------------------------------------
Reporter: BorisZZZ | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* type: Bug => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
I think we could error out which a more appropriate message but it will be
very hard to make the above queryset work since `OuterRef` cannot be
resolved to a proper `output_field` until its queryset gets annotated to
an outer query. I guess we could allow an `output_field` to be specified
on `OuterRef` initialization to allow `filter` to reference it before it's
resolved to a `Col`.
--
Ticket URL: <https://code.djangoproject.com/ticket/31714#comment:1>
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/066.a68620b4b039ea2672ac6e2ee4c5c85f%40djangoproject.com.
