Speaking of timestamps, I think it would be convenient to have a
single-word alias for "timestamp with time zone". This is the date
type I use almost exclusively and its name is annoyingly big.
On Sat, Nov 28, 2009 at 6:57 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Eduardo Piombino <drakorg(at)gmail(dot)com> writes:
>> I see current criteria and all the SQL-standard compliance policy, but
>> wouldn't it still make sense to be able to store a date reference, along
>> with a time zone reference?
>> Wouldn't it be useful, wouldn't it be elegant?
> It seems pretty ill-defined to me, considering that many jurisdictions
> don't switch daylight savings time at local midnight. How would you
> know which zone applied on a DST transition date?
>> On the other hand, I don't really see the reasons of this statement:
>> "Although the date type *cannot *have an associated time zone, the time type
>> Why is this so?
> Because the SQL committee were smoking something strange that day.
> You won't find anybody around here who will defend the existence of
> TIME WITH TIME ZONE. We only put it in for minimal spec compliance.
> regards, tom lane
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
In response to
pgsql-general by date
|Next:||From: Scott Marlowe||Date: 2009-11-29 02:44:30|
|Subject: Re: Date with time zone|
|Previous:||From: Tomas Lanczos||Date: 2009-11-29 00:22:24|
|Subject: Re: incorrect restore from pg_dumpall|