#30719: Unable to use OuterRef(Expression(...))
-------------------------------------+-------------------------------------
Reporter: Matthew Schinckel | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: Subquery, OuterRef, | Triage Stage:
Expression | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
> I'll close this (and the PR), but I still have an itchy feeling that
there is a use-case for having an expression inside the OuterRef - but
maybe it's always that the Expression itself would just have the OuterRef
inside it...
I think this should not happen; we don't allow expressions in `F` either
since it's just an unresolved reference to a column. In a sense `OuterRef`
is really just a way to express `F` for an outer query.
--
Ticket URL: <https://code.djangoproject.com/ticket/30719#comment:4>
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/067.97b562777493d4b3f584cbef1eb6e34f%40djangoproject.com.
