From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
Cc: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: timestamp with time zone a la sql99 |
Date: | 2004-10-22 14:13:18 |
Message-ID: | 6540.1098454398@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> In a fit of early morning, pre-coffee thoughts, I'm thinking this might be
> just what I've been looking for. In one of my apps we take calls from around
> the country for customers and store the time that call came in. Unfortunately
> we need to know things like how many calls did we take in an hour across
> customers, but also how many calls did we take at 6AM local time to the
> customer. The way PostgreSQL works now, you have to store some extra bits
> of info in another column and then reassemble it to be able to determine
> those two queries, but it sounds like your timestampstdtz would allow that
> information to be stored together, as it should be.
As far as I can tell, Dennis is planning slavish adherence to the spec,
which will mean that the datatype is unable to cope effectively with
daylight-savings issues. So I'm unconvinced that it will be very
helpful to you for remembering local time in addition to true
(universal) time.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-10-22 14:21:50 | Re: SET SESSION SESSION AUTHORIZATION |
Previous Message | Jan Wieck | 2004-10-22 13:36:10 | Re: [Slony1-general] Re: Slony-I 1.0.4 Released |