mirror of
https://github.com/django/django.git
synced 2025-10-09 06:49:12 +00:00
a150160c9f
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.
23 lines
811 B
Plaintext
23 lines
811 B
Plaintext
==========================
|
|
Django 5.2.4 release notes
|
|
==========================
|
|
|
|
*Expected July 2, 2025*
|
|
|
|
Django 5.2.4 fixes several bugs in 5.2.3.
|
|
|
|
Bugfixes
|
|
========
|
|
|
|
* Fixed a regression in Django 5.2.2 where :meth:`HttpRequest.get_preferred_type()
|
|
<django.http.HttpRequest.get_preferred_type>` incorrectly preferred more
|
|
specific media types with a lower quality (:ticket:`36447`).
|
|
|
|
* 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`).
|