diff options
Diffstat (limited to 'docs/ref/models')
| -rw-r--r-- | docs/ref/models/expressions.txt | 11 |
1 files changed, 8 insertions, 3 deletions
diff --git a/docs/ref/models/expressions.txt b/docs/ref/models/expressions.txt index 5dadf35873..24e4f42834 100644 --- a/docs/ref/models/expressions.txt +++ b/docs/ref/models/expressions.txt @@ -257,7 +257,10 @@ placeholder within the ``template``. The ``output_field`` argument requires a model field instance, like ``IntegerField()`` or ``BooleanField()``, into which Django will load the value -after it's retrieved from the database. +after it's retrieved from the database. Usually no arguments are needed when +instantiating the model field as any arguments relating to data validation +(``max_length``, ``max_digits``, etc.) will not be enforced on the expression's +output value. Note that ``output_field`` is only required when Django is unable to determine what field type the result should be. Complex expressions that mix field types @@ -318,8 +321,10 @@ values into their corresponding database type. The ``output_field`` argument should be a model field instance, like ``IntegerField()`` or ``BooleanField()``, into which Django will load the value -after it's retrieved from the database. - +after it's retrieved from the database. Usually no arguments are needed when +instantiating the model field as any arguments relating to data validation +(``max_length``, ``max_digits``, etc.) will not be enforced on the expression's +output value. Technical Information ===================== |