From cbdf128cb316bccf9ca3b3b4966e57bd050bfc8a Mon Sep 17 00:00:00 2001 From: Hal Blackburn Date: Tue, 4 Nov 2025 05:58:46 +0000 Subject: [5.2.x] Fixed #36704 -- Fixed system check error for proxy model with a composite pk. 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. Backport of 74564946c3b42a2ef7d087047e49873847a7e1d9 from main. --- docs/releases/5.2.8.txt | 3 +++ 1 file changed, 3 insertions(+) (limited to 'docs/releases') diff --git a/docs/releases/5.2.8.txt b/docs/releases/5.2.8.txt index a75db9cbc8..62cb32f55c 100644 --- a/docs/releases/5.2.8.txt +++ b/docs/releases/5.2.8.txt @@ -16,3 +16,6 @@ Bugfixes * 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. -- cgit v1.3