From: | Thom Brown <thombrown(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Revert removal of pre-7.4 documenation behavior mentions. |
Date: | 2010-02-24 18:33:44 |
Message-ID: | bddc86151002241033p5e1f72dfjd3d0817c27429c6b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On 24 February 2010 17:07, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Tom Lane wrote:
>> Thom Brown <thombrown(at)gmail(dot)com> writes:
>> > On 24 February 2010 15:54, Bruce Momjian <momjian(at)postgresql(dot)org> wrote:
>> > + Prior to <productname>PostgreSQL</productname> 7.3, writing just
>> > + <type>timestamp</type> was equivalent to <type>timestamp with
>> > + time zone</type>. This was changed for SQL compliance.
>>
>> > You may wish to say what exactly it was changed to.
>>
>> The previous para says that.
>
> Uh, well, the chart says it via syntax, which isn't exactly the same as
> stating it, and this is particularly important because it is an odd
> default.
>
> I have created an updated paragraph for that section:
>
> http://momjian.us/tmp/pgsql/datatype-datetime.html
>
> 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).
>
> Is that an improvement?
>
Yes, that's clearer, even if that information is inferred in the table
above (my bad, I should have checked that too).
Thanks,
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2010-02-24 18:34:40 | Re: pgsql: Remove stray semicolon, per report from strk |
Previous Message | David Fetter | 2010-02-24 18:21:43 | Re: pgsql: Remove stray semicolon, per report from strk |