#31135: OuterRef generates invalid SQL with __in filter.
-------------------------------------+-------------------------------------
Reporter: Bernd Wechner | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution: invalid
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 Mariusz Felisiak):
> It remains a bug that it produces invalid SQL where a prior version did
not, ...
Yes but unintentionally and only on some databases.
> and not a sensible exception - causing much wasted time on the part of
anyone who used the old
Feel-free to prepare a patch with raising a Python level error when using
many-to-many field in `F()` or `OuterRef()` (see also #32414). I would be
happy to review.
--
Ticket URL: <https://code.djangoproject.com/ticket/31135#comment:7>
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/01070180b24c007e-9833fbb4-e098-4be6-afbb-96799779998b-000000%40eu-central-1.amazonses.com.
