diff options
| author | Josh Smeaton <josh.smeaton@gmail.com> | 2014-12-01 17:11:23 +1100 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-12-12 10:17:48 -0500 |
| commit | 267a1dcd9b7877d97917ba6222fd247da060f9b0 (patch) | |
| tree | 70399202a3ad907f0be364a7c2be865b6923fc01 /docs/ref | |
| parent | e2868308bfa4ec165fb54b6128ee18a7b4d50643 (diff) | |
Fixed #23941 -- Removed implicit decimal formatting from expressions.
Diffstat (limited to 'docs/ref')
| -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 ===================== |