These are all pretty obscure. How do I make them prominent without
really scaring people who don't even know what they are?
> I am aware of at least three non-backward-compatible changes in 7.0,
> ie, things that will break existing applications in perhaps non-obvious
> ways. I think the "Release Notes" document ought to call these out in a
> separate section, rather than expecting people to examine the detailed
> change list and intuit what those brief entries mean to them.
> The three I can think of are:
> 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 :
> Any others?
> regards, tom lane
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
In response to
pgsql-hackers by date
|Next:||From: Benjamin Adida||Date: 2000-04-02 21:47:25|
|Subject: Re: 7.0 release notes should call out incompatiblechanges more clearly|
|Previous:||From: Thomas Lockhart||Date: 2000-04-02 21:37:43|
|Subject: Re: Call for porting reports|