From a5ee682baf31755ce1c1121d116e6d7e9cd486ef Mon Sep 17 00:00:00 2001 From: Giannis Terzopoulos Date: Wed, 15 Nov 2023 13:48:45 +0100 Subject: [PATCH] [5.0.x] Removed obsolete sentence in custom model field docs. Backport of 36ed45d27cb97fe3a41eca219ba75ff69f16b93c from main --- docs/howto/custom-model-fields.txt | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/howto/custom-model-fields.txt b/docs/howto/custom-model-fields.txt index fa5c4389d7..1e7ac4f0ba 100644 --- a/docs/howto/custom-model-fields.txt +++ b/docs/howto/custom-model-fields.txt @@ -431,9 +431,7 @@ Django when the framework constructs the ``CREATE TABLE`` statements for your application -- that is, when you first create your tables. The methods are also called when constructing a ``WHERE`` clause that includes the model field -- that is, when you retrieve data using QuerySet methods like ``get()``, -``filter()``, and ``exclude()`` and have the model field as an argument. They -are not called at any other time, so it can afford to execute slightly complex -code, such as the ``connection.settings_dict`` check in the above example. +``filter()``, and ``exclude()`` and have the model field as an argument. Some database column types accept parameters, such as ``CHAR(25)``, where the parameter ``25`` represents the maximum column length. In cases like these,