From acc9a95b6354d7c15797627d2ab3d11f687f1620 Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Thu, 8 Mar 2007 03:41:04 +0000 Subject: [PATCH] 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 --- django/conf/project_template/settings.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/django/conf/project_template/settings.py b/django/conf/project_template/settings.py index d36553b84d..cadb5146b7 100644 --- a/django/conf/project_template/settings.py +++ b/django/conf/project_template/settings.py @@ -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'