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/topics | |
| 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/topics')
| -rw-r--r-- | docs/topics/i18n/timezones.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/topics/i18n/timezones.txt b/docs/topics/i18n/timezones.txt index 0b0e0d136c..df9d1decfc 100644 --- a/docs/topics/i18n/timezones.txt +++ b/docs/topics/i18n/timezones.txt @@ -9,13 +9,13 @@ Time zones Overview ======== -When support for time zones is enabled, Django stores date and time +When support for time zones is enabled, Django stores datetime information in UTC in the database, uses time-zone-aware datetime objects internally, and translates them to the end user's time zone in templates and forms. This is handy if your users live in more than one time zone and you want to -display date and time information according to each user's wall clock. +display datetime information according to each user's wall clock. Even if your Web site is available in only one time zone, it's still good practice to store data in UTC in your database. One main reason is Daylight |