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@xxxxxxxxxxxxx> wrote: > Eduardo Piombino <drakorg@xxxxxxxxx> 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 >> can." >> 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@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general > -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
