|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>|
|Subject:||Re: timestamp with time zone a la sql99|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> writes:
> I've made a partial implementation of a datatype "timestamp with time
> zone" as described in the sql standard. The current type "timestamptz"
> does not store the time zone as a standard one should do.
I'm aware that there are aspects of the spec behavior that appear to
require that, but is it really an improvement over the implementation
we have? This is an area in which the standard is pretty brain-dead
--- the entire concept of a "time with time zone" datatype is rather
suspect, for instance.
In particular, I wonder how you will handle daylight-savings issues.
The spec definition seems to preclude doing anything intelligent with
DST, as they equate a timezone with a fixed offset from UTC. That's
not how it works in (large parts of) the real world.
regards, tom lane
|Next Message||Tom Lane||2004-10-21 14:58:41||Re: BUG #1290: Default value and ALTER...TYPE|
|Previous Message||Dennis Bjorklund||2004-10-21 11:22:40||timestamp with time zone a la sql99|