Re: Calendar vs. Timestamp

> > Is 8.1 driver compatible with PG 8.0? I can easily update the PG
> > version on my development box. But, it wouldn't easy for the
> > deployment box.
> >
>
> Yes, the 8.1 driver is backward compatible with all server releases
> back to 7.2. As always it's good to test on your development box
> first, but I don't see any problems with an upgrade.
>

After having a 8.1 driver, the timestamp is stored correctly in the DB. So, it indeed is a bug in the 8.0 driver.

I would like to clarify one observation. The timestamp seems only take the date section data of a calendar object regardless the value of the time zone. If so, a calendar object with a specified time zone would not make any difference in comparsion to a calendar object with the default time zone. Or, the default time zone is always used in PG.

Thanks.

--
_______________________________________________

Search for businesses by name, location, or phone number. -Lycos Yellow Pages

http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10

On Tue, 11 Apr 2006, Wei Wei wrote:

> I would like to clarify one observation. The timestamp seems only take
> the date section data of a calendar object regardless the value of the
> time zone. If so, a calendar object with a specified time zone would not
> make any difference in comparsion to a calendar object with the default
> time zone. Or, the default time zone is always used in PG.
>

I think the confusion arises from the fact that the server always stores
timestamps in utc and always returns them based upon the current setting
of the TimeZone configuration parameter.

CREATE TABLE tstest(a timestamptz);
INSERT INTO tstest VALUES ('2006-04-11 16:15:28-07');
INSERT INTO tstest VALUES ('2006-04-11 16:15:28-08');
SET TimeZone = 'America/Los_Angeles';
INSERT INTO tstest VALUES ('2006-04-11 16:15:28');
SELECT * FROM tstest;
SET TimeZone = 'America/New_York';
INSERT INTO tstest VALUES ('2006-04-11 16:15:28');
SELECT * FROM tstest;

Kris Jurka