Fixed #2315 -- Clarified that the available PostgreSQL timezone options may

provide more options than are strictly available. This is probably the best we
can do for such a varied area of standardisation.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@4678 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2007-03-08 03:41:04 +00:00
parent a89b51b033
commit acc9a95b63
1 changed files with 2 additions and 1 deletions

View File

@ -16,8 +16,9 @@ DATABASE_PASSWORD = '' # Not used with sqlite3.
DATABASE_HOST = '' # Set to empty string for localhost. Not used with sqlite3.
DATABASE_PORT = '' # Set to empty string for default. Not used with sqlite3.
# Local time zone for this installation. All choices can be found here:
# Local time zone for this installation. Choices can be found here:
# http://www.postgresql.org/docs/8.1/static/datetime-keywords.html#DATETIME-TIMEZONE-SET-TABLE
# although not all variations may be possible on all operating systems.
# If running in a Windows environment this must be set to the same as your
# system time zone.
TIME_ZONE = 'America/Chicago'