summaryrefslogtreecommitdiff
path: root/docs/howto
diff options
context:
space:
mode:
authorGiannis Terzopoulos <terzo.giannis@gmail.com>2023-11-15 13:48:45 +0100
committerGitHub <noreply@github.com>2023-11-15 13:48:45 +0100
commit36ed45d27cb97fe3a41eca219ba75ff69f16b93c (patch)
tree875f28783e74b4861fa8f276d00a058a955e3248 /docs/howto
parent640283711e6c8d25ad0e3c97453cd178a3e4d6a6 (diff)
Removed obsolete sentence in custom model field docs.
Diffstat (limited to 'docs/howto')
-rw-r--r--docs/howto/custom-model-fields.txt4
1 files changed, 1 insertions, 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,