From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-sql@postgresql.org
Subject: Re: Assigning a timestamp without timezone to a timestamp
Date: Thu, 5 Oct 2006 16:31:21 -0400
Message-ID: <20061005203121.GI8826@phlogiston.dyndns.org> (raw)
In-Reply-To: <6667446.post@talk.nabble.com>
References: <6613652.post@talk.nabble.com>
<20061003135623.GB3191@phlogiston.dyndns.org>
<6621346.post@talk.nabble.com>
<20061003145134.GA3399@phlogiston.dyndns.org>
<8C5B026B51B6854CBE88121DBF097A864DE848@ehost010-33.exch010.intermedia.net>
<20061005183128.GD8826@phlogiston.dyndns.org>
<6667446.post@talk.nabble.com>
On Thu, Oct 05, 2006 at 01:06:00PM -0700, chrisj wrote:
> If only all time zones were fixed offset timezones life would be so much
> simpler.
Indeed.
> Unfortunately the main area of deployment of my app will beToronto which is
> on EDT which is not a fixed offsets timezone. I hope/assume your solution
> works with "EDT" instead of "-3", I will test it soon.
Should do, although you'll need more than EDT. EDT is also fixed:
it's UTC-4. EST5EDT isn't, though, so you could use that (you'd need
to improve your schema, though, because you had char(3) there, and
not all time zones are 3 characters long). But to answer your
question, yes, it works. I just tried it.
A
--
Andrew Sullivan | ajs@crankycanuck.ca
Information security isn't a technological problem. It's an economics
problem.
--Bruce Schneier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: ajs@crankycanuck.ca
Subject: Re: Assigning a timestamp without timezone to a timestamp
In-Reply-To: <20061005203121.GI8826@phlogiston.dyndns.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox