#28497: QuerySet.filter() with a sliced QuerySet crashes
-------------------------------------+-------------------------------------
Reporter: Sergey Fedoseev | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Release blocker | 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):
* cc: Simon Charette (added)
Comment:
We should try to error out with a more appropriate message but I don't
think we ever officially supported passing a queryset to an `__exact`
lookup. I vaguely remember a ticket about it but I can't find it anymore.
I think you should be using an `__in` lookup instead as your query will
fail with `more than one row returned by a subquery used as an expression`
as soon as the table backing up your ` Skill` model has more than two
rows.
--
Ticket URL: <https://code.djangoproject.com/ticket/28497#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.8f189437bf9d8fbaabd454941afd5252%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
