diff options
| author | Simon Charette <charette.s@gmail.com> | 2025-06-14 11:04:17 -0400 |
|---|---|---|
| committer | Natalia <124304+nessita@users.noreply.github.com> | 2025-06-30 20:16:08 -0300 |
| commit | a150160c9fc6ba6220f1e63863b03e7f7978b747 (patch) | |
| tree | 0aea5b13e19b4d06442376f94c406e00838bffda /docs | |
| parent | db5da3c91c3122300680c4e7200a463273a5351e (diff) | |
[5.2.x] Fixed #36464 -- Fixed "__in" tuple lookup on backends lacking native support.
When native support for tuple lookups is missing in a DB backend, it can
be emulated with an EXISTS clause. This is controlled by the backend
feature flag "supports_tuple_lookups".
The mishandling of subquery right-hand side in `TupleIn` (added to
support `CompositePrimaryKey` in Refs #373) was likely missed because
the only core backend we test with the feature flag disabled
(Oracle < 23.4) supports it natively.
Thanks to Nandana Raol for the report, and to Sarah Boyce, Jacob Walls,
and Natalia Bidart for reviews.
Backport of 192bc7a7be92e20cc250907fb4083df689715679 from main.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/releases/5.2.4.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/releases/5.2.4.txt b/docs/releases/5.2.4.txt index 521ed94d6c..31f4b8984f 100644 --- a/docs/releases/5.2.4.txt +++ b/docs/releases/5.2.4.txt @@ -16,3 +16,7 @@ Bugfixes * Fixed a regression in Django 5.2.3 where ``Value(None, JSONField())`` used in a :class:`~django.db.models.expressions.When` condition was incorrectly serialized as SQL ``NULL`` instead of JSON ``null`` (:ticket:`36453`). + +* Fixed a crash in Django 5.2 when performing an ``__in`` lookup involving a + composite primary key and a subquery on backends that lack native support for + tuple lookups (:ticket:`36464`). |