Opened 19 years ago
Closed 19 years ago
#1823 closed defect (invalid)
set timezone in pgsql is not working right
Reported by: | Owned by: | Adrian Holovaty | |
---|---|---|---|
Component: | contrib.admin | Version: | dev |
Severity: | normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
set timezone command for postgres is currently "set time zone . . ." which crashes.
should be "set timezone to"
=================================================================== --- django/db/backends/postgresql/base.py (revision 2868) +++ django/db/backends/postgresql/base.py (working copy) @@ -39,7 +39,7 @@ self.connection = Database.connect(conn_string) self.connection.set_isolation_level(1) # make transactions transparent to all cursors cursor = self.connection.cursor() - cursor.execute("SET TIME ZONE %s", [settings.TIME_ZONE]) + cursor.execute("SET TIMEZONE %s", [settings.TIME_ZONE]) if settings.DEBUG: return util.CursorDebugWrapper(cursor, self) return cursor
Thanks,
Kelly
Change History (3)
comment:1 by , 19 years ago
comment:3 by , 19 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Adrian,
Sorry for the annoyance,
When I was first going through the tutorial,
I had a problem (error) that showed the SET TIME ZONE in the error.
your syntax for set time zone works fine at the sql prompt.
Hitting tab-complete at the postgres prompt changes it to TIMEZONE which is what made me think that was the problem.
I have not been able to re-create so I'm going to mark resolved as 'stupid user error'
Thanks,
Kelly
I'm wondering why this has worked, in its current form, for several years. Are you on a peculiar version of Postgres?