From: | Benjamin Adida <ben(at)mit(dot)edu> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 7.0 release notes should call out incompatible changes more clearly |
Date: | 2000-04-02 21:47:25 |
Message-ID: | B50D382D.1996%ben@mit.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
on 4/2/00 5:40 PM, Bruce Momjian at pgman(at)candle(dot)pha(dot)pa(dot)us wrote:
>> 1. If a GROUP BY item matches both an input column name and a
>> select-list label ("AS" name), 7.0 assumes the input column is meant.
>> This is compliant with the SQL92 spec. Unfortunately older versions
>> made the opposite choice.
>>
>> 2. SELECT DISTINCT ON syntax has changed --- now need parentheses
>> around the item being DISTINCT'ed.
>>
>> 3. User-defined operator names can't end in "+" or "-" unless they
>> also contain ~ ! @ # % ^ & | ` ? $ or :
Unless I've missed some earlier discussion of it, the grammar for adding a
field to a table has also changed.
In 6.5, you could do
alter table add (
id integer
);
whereas in 7.0 you must do
alter table add id integer;
and the parens will screw things up.
-Ben
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 2000-04-02 21:50:41 | Re: Docs refreshed |
Previous Message | Bruce Momjian | 2000-04-02 21:40:03 | Re: 7.0 release notes should call out incompatible changes more clearly |