mirror of
https://github.com/django/django.git
synced 2025-11-07 07:15:35 +00:00
74564946c3
Proxy models subclassing a model with a CompositePrimaryKey were incorrectly reporting check errors because the check that requires only local fields to be used in a composite pk was evaluated against the proxy subclass, which has no fields. To fix this, composite pk field checks are not evaluated against proxy subclasses, as none of the checks are applicable to proxy subclasses. This also has the benefit of not double-reporting real check errors from an invalid superclass pk. Thanks Clifford Gama for the review.
22 lines
692 B
Plaintext
22 lines
692 B
Plaintext
==========================
|
|
Django 5.2.8 release notes
|
|
==========================
|
|
|
|
*November 5, 2025*
|
|
|
|
Django 5.2.8 fixes one security issue with severity "high", one security issue
|
|
with severity "moderate", and several bugs in 5.2.7. It also adds compatibility
|
|
with Python 3.14.
|
|
|
|
Bugfixes
|
|
========
|
|
|
|
* Added compatibility for ``oracledb`` 3.4.0 (:ticket:`36646`).
|
|
|
|
* Fixed a bug in Django 5.2 where ``QuerySet.first()`` and ``QuerySet.last()``
|
|
raised an error on querysets performing aggregation that selected all fields
|
|
of a composite primary key.
|
|
|
|
* Fixed a bug in Django 5.2 where proxy models having a ``CompositePrimaryKey``
|
|
incorrectly raised a ``models.E042`` system check error.
|