From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
---|---|
To: | "'lockhart(at)fourpalms(dot)org'" <lockhart(at)fourpalms(dot)org> |
Cc: | Hackers List <pgsql-hackers(at)postgresql(dot)org> |
Subject: | AW: AW: timestamp in pg_dump |
Date: | 2001-02-08 09:17:34 |
Message-ID: | 11C1E6749A55D411A9670001FA6879633681EC@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > But the current timestamp does not store a timezone. timestamp with time zone
> > is supposed to store and output the timezone that was inserted.
> > The current timestamp has it messed up (sorry), since it does not store a timezone.
> > It stores time in UTC and always converts output to the timezone derived from [PG]TZ.
>
> Good point, but I'll disagree with the implied conclusion. imho the
> SQL9x provisions for time zone handling are fundamentally and tragically
> broken, with absolutely no provisions for DST, time zone shifting, etc
> etc. Which helps lead most folks to code other databases without time
> zones at all.
Ok, so you would be free to create a differently named type that does whatever
you like, but imho an ANSI standard type should behave exactly as defined.
Especially if it has such a verbose name as "timestamp with time zone".
My experience is, that developers don't use database supplied time types,
because they all behave differently, not because they are not useful.
I think we should not create yet another behavior.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Georges Martin | 2001-02-08 10:24:22 | CORBA? |
Previous Message | Nathan Myers | 2001-02-08 05:33:47 | Re: PL/pgsql EXECUTE 'SELECT INTO ...' |