#33769: F() expressions - OperationalError
-------------------------------+------------------------------------
Reporter: Pablo | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 3.2
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
-------------------------------+------------------------------------
Comment (by Simon Charette):
I'd be curious to see what kind of queries it generated on Django 2.2.
I would assume that a `LEFT JOIN` is generated for
`shifts_season_chief_tipes` and that the where clause has a
`shifts_workshift.type_id IN (shifts_season_chief_tipes.workshifttype_id)`
which is basically equivalent to `shifts_workshift.type_id =
shifts_season_chief_tipes.workshifttype_id`.
Given we've taken a stance that we don't want to explicitly support
`__exact=Queryset` (single-valued lhs with multi-valued rhs) I thought
we'd want to do the same with `__in=F('m2m')` (multi-valued lhs with
single-valued rhs).
--
Ticket URL: <https://code.djangoproject.com/ticket/33769#comment:3>
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/01070181393d35f0-87df3a84-02e2-44b5-b31e-7eb4256699ae-000000%40eu-central-1.amazonses.com.
