From 6025eab3c509b4de922117e16866bbfe0ee99aa6 Mon Sep 17 00:00:00 2001 From: Nilesh Kumar Pahari Date: Thu, 18 Dec 2025 16:21:50 +0530 Subject: Fixed #36806 -- Added system check for null kwarg in GeneratedField. The null argument has no effect on GeneratedField since the nullability of the column depends on the database and expression used. --- docs/ref/checks.txt | 1 + docs/ref/models/fields.txt | 3 +++ 2 files changed, 4 insertions(+) (limited to 'docs/ref') diff --git a/docs/ref/checks.txt b/docs/ref/checks.txt index 1e56464a6f..7250df692f 100644 --- a/docs/ref/checks.txt +++ b/docs/ref/checks.txt @@ -221,6 +221,7 @@ Model fields ``GeneratedField``\s. * **fields.E223**: ``GeneratedField.output_field`` has errors: ... * **fields.W224**: ``GeneratedField.output_field`` has warnings: ... +* **fields.W225**: ``null`` has no effect on ``GeneratedField``. * **fields.E900**: ``IPAddressField`` has been removed except for support in historical migrations. * **fields.W900**: ``IPAddressField`` has been deprecated. Support for it diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index a87d7261a7..fe4d764ab3 100644 --- a/docs/ref/models/fields.txt +++ b/docs/ref/models/fields.txt @@ -1377,6 +1377,9 @@ materialized view. backends that support it (SQLite, PostgreSQL, and Oracle) and marked as deferred otherwise. +:attr:`~Field.null` has no effect on ``GeneratedField`` since whether the +column is nullable depends on the database and expression used. + ``GenericIPAddressField`` ------------------------- -- cgit v1.3