diff options
| author | Christopher Luc <chris.luc.dev@gmail.com> | 2015-03-21 17:45:42 -0700 |
|---|---|---|
| committer | Markus Holtermann <info@markusholtermann.eu> | 2015-03-29 22:32:05 +0200 |
| commit | 8119876d4a533fbc2ba4d1c30eaddbcc28119488 (patch) | |
| tree | 53be5f6c8a79e867fa3504ef018c500d78a0dcda /docs/ref/models | |
| parent | 75430be86f4c90b7fb8a370d2b080a8a7cc925a0 (diff) | |
Improved docs for timezone handling for auto_now and auto_now_add
Thanks djbug for the report and Aymeric Augustin and Carl Meyer for the
review.
Diffstat (limited to 'docs/ref/models')
| -rw-r--r-- | docs/ref/models/fields.txt | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index 3dd0e41e7a..01ff654353 100644 --- a/docs/ref/models/fields.txt +++ b/docs/ref/models/fields.txt @@ -505,6 +505,15 @@ Any combination of these options will result in an error. ``True`` will cause the field to have ``editable=False`` and ``blank=True`` set. +.. note:: + The ``auto_now`` and ``auto_now_add`` options will always use the date in + the :ref:`default timezone <default-current-time-zone>` at the moment of + creation or update. If you need something different, you may want to + consider simply using your own callable default or overriding ``save()`` + instead of using ``auto_now`` or ``auto_now_add``; or using a + ``DateTimeField`` instead of a ``DateField`` and deciding how to handle the + conversion from datetime to date at display time. + ``DateTimeField`` ----------------- |
