#33808: Specific subquery produces wrong SQL (error 500)
-------------------------------------+-------------------------------------
Reporter: Fabio Zoratti | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: database, count, | Triage Stage:
query, orm | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => duplicate
Comment:
Thanks for the report, however #32673 is a regression in Django 3.0
reported when it was already EOL. Per our backporting policy this means it
doesn't qualify for a backport to 3.2.x anymore. See
[https://docs.djangoproject.com/en/stable/internals/release-process/
Django’s release process] for more details. Also, Django 3.2 is in
extended support so it doesn't receive bugfixes anymore (except security
patches).
Moreover, using the `__in` lookup with `ManyToManyField` has never been
officially supported, you should use `Q(sm_f1=F("sm_f2"))` instead of
`Q(sm_f1__in=F("sm_f2"))`, it's a duplicate of #31135.
--
Ticket URL: <https://code.djangoproject.com/ticket/33808#comment:5>
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/010701819926027d-3287335c-64bc-41d4-9c35-f261d01e40da-000000%40eu-central-1.amazonses.com.
