Robert Treat <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
