Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
I'm confused as to what's going on with a PostgreSQL "timestamp" type
converted back to string. The field in question is a "timestamp without
Selecting my timestamp from PostgreSQL via psql gives:
Yet in my code, when I str() or mx.DateTime.ISO.strUTC() the mx.DateTime
representation of the field returned by pyPgSQL, I get
I'm currently in UTC+11 (10+summer)
Any suggestions as to what might be happening here?
When I first connect to PostgreSQL, I always SET TIME ZONE 'UTC'.
PS> Cross-posted to the Egenix mailing list
On Thu, Jan 13, 2011 at 09:56:49AM +1100, Kingsley Turner wrote:
> 2011-01-13 08:54:11+0000
> When I first connect to PostgreSQL, I always SET TIME ZONE 'UTC'.
UTC *is* +0000 ?
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346