Date: Tue, 3 Oct 2006 10:51:34 -0400
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: chrisj <chrisj.wood@sympatico.ca>
Cc: pgsql-sql@postgresql.org
Subject: Re: Assigning a timestamp without timezone to a timestamp
Message-ID: <20061003145134.GA3399@phlogiston.dyndns.org>
References: <6613652.post@talk.nabble.com>
	<20061003135623.GB3191@phlogiston.dyndns.org>
	<6621346.post@talk.nabble.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6621346.post@talk.nabble.com>
User-Agent: Mutt/1.5.9i

On Tue, Oct 03, 2006 at 07:26:52AM -0700, chrisj wrote:
> location, but they are the directive to all store locations saying: "In the
> context of the timezone your store is located in,  these are the hours you
> should be open.

Ah.  Well, then, right, it _does_ have to be timezone free.  That's
actually the only case I'd use that.  Sorry, I'm dim, and didn't
understand properly what you were doing.  (I read the "relative to
the store's own time zone" to refer to the corporate office.  No, I
don't know why, either.  Told you I'm dim.)

Anyway, here's something that worked for me (expanding this into your
case ought not to be too tricky):

testing=# SELECT * from storetz ;
 id | timezone 
----+----------
  1 | -03
(1 row)

testing=# SELECT a.timestamp::timestamptz from (SELECT '2006-10-03
09:00'||"timezone" as timestamp from storetz where id = 1) as a;
       timestamp        
------------------------
 2006-10-03 12:00:00+00
(1 row)

A
-- 
Andrew Sullivan  | ajs@crankycanuck.ca
When my information changes, I alter my conclusions.  What do you do sir?
		--attr. John Maynard Keynes