From de9f46d7074a948d781b31476bb12a3ed017c8c0 Mon Sep 17 00:00:00 2001 From: Jacob Walls Date: Tue, 14 Jan 2025 16:44:17 +0100 Subject: [PATCH] Fixed #36070 -- Clarified model validation behavior for composite pks. --- docs/topics/composite-primary-key.txt | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/topics/composite-primary-key.txt b/docs/topics/composite-primary-key.txt index 883c1b3e6f..68356593b4 100644 --- a/docs/topics/composite-primary-key.txt +++ b/docs/topics/composite-primary-key.txt @@ -186,6 +186,16 @@ field :exc:`.FieldError`. :attr:`.Field.editable` to ``False`` on all primary key fields to exclude them from ModelForms. +Composite primary keys in model validation +========================================== + +Since ``pk`` is only a virtual field, including ``pk`` as a field name in the +``exclude`` argument of :meth:`.Model.clean_fields` has no effect. To exclude +the composite primary key fields from +:ref:`model validation `, specify each field individually. +:meth:`.Model.validate_unique` can still be called with ``exclude={"pk"}`` to +skip uniqueness checks. + Building composite primary key ready applications =================================================