From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | sad <sad(at)bestmx(dot)ru>, pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: Top five challenges |
Date: | 2011-03-10 16:01:57 |
Message-ID: | 201103101601.p2AG1vW14016@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-www |
Alvaro Herrera wrote:
> Excerpts from sad's message of mi mar 02 10:23:53 -0300 2011:
> > On Mar 2 2011, Josh Berkus wrote:
>
> > >> 3. To make TIMESTAMPTZ useful by introducing proper type cast
> > >> TIMESTAMPTZ to TIMESTAMP
> > >
> > >Why are you using Timestamp-no-tz at all? I was thinking we should
> > >change the default ...
> >
> > Why did u introduced it?
>
> The standard requires the current behavior. It's not going to change.
> It changed in 7.1 or so.
And we document why the default is so odd:
http://www.postgresql.org/docs/9.0/static/datatype-datetime.html#DATATYPE-TIMEZONES
Note: The SQL standard requires that writing just timestamp be
equivalent to timestamp without time zone, and PostgreSQL honors that
behavior. (Releases prior to 7.3 treated it as timestamp with time
zone.)
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-03-10 16:45:02 | Re: Top five challenges |
Previous Message | Bruce Momjian | 2011-03-10 16:00:03 | Re: Top five challenges |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-03-10 16:45:02 | Re: Top five challenges |
Previous Message | Bruce Momjian | 2011-03-10 16:00:03 | Re: Top five challenges |