Skip site navigation (1) Skip section navigation (2)

Re: Date with time zone

From: silly8888 <silly8888(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Eduardo Piombino <drakorg(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, Adrian Klaver <aklaver(at)comcast(dot)net>
Subject: Re: Date with time zone
Date: 2009-11-29 02:25:27
Message-ID: 3c8f9f940911281825o5d1502a5we97e06ae1ebc43e5@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
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
>> 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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

In response to

Responses

pgsql-general by date

Next:From: Scott MarloweDate: 2009-11-29 02:44:30
Subject: Re: Date with time zone
Previous:From: Tomas LanczosDate: 2009-11-29 00:22:24
Subject: Re: incorrect restore from pg_dumpall

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group