mirror of
https://github.com/django/django.git
synced 2025-05-28 17:56:29 +00:00
Removed obsolete sentence in custom model field docs.
This commit is contained in:
parent
640283711e
commit
36ed45d27c
@ -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
|
application -- that is, when you first create your tables. The methods are also
|
||||||
called when constructing a ``WHERE`` clause that includes the model field --
|
called when constructing a ``WHERE`` clause that includes the model field --
|
||||||
that is, when you retrieve data using QuerySet methods like ``get()``,
|
that is, when you retrieve data using QuerySet methods like ``get()``,
|
||||||
``filter()``, and ``exclude()`` and have the model field as an argument. They
|
``filter()``, and ``exclude()`` and have the model field as an argument.
|
||||||
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.
|
|
||||||
|
|
||||||
Some database column types accept parameters, such as ``CHAR(25)``, where the
|
Some database column types accept parameters, such as ``CHAR(25)``, where the
|
||||||
parameter ``25`` represents the maximum column length. In cases like these,
|
parameter ``25`` represents the maximum column length. In cases like these,
|
||||||
|
Loading…
x
Reference in New Issue
Block a user