#28664: basic subquery generates invalid sql
-------------------------------------+-------------------------------------
Reporter: David Szotten | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
The current consensus in #28497 would be to officialize the support of
`__eq=queryset`.
Note that they won't be any way from protecting you from passing a
queryset returning more than a single result and ending up with a `more
than one row returned by a subquery used as an expression` or similar
message from the database. You'll have to make sure the provided filters
don't match more than a single row or that you `LIMIT` your query.
--
Ticket URL: <https://code.djangoproject.com/ticket/28664#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.34eedd87c3ccac692827416dd849565b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
