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

7.0 release notes should call out incompatible changes more clearly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: 7.0 release notes should call out incompatible changes more clearly
Date: 2000-04-02 21:13:03
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
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


pgsql-hackers by date

Next:From: Peter EisentrautDate: 2000-04-02 21:17:59
Subject: Re: --enable-locale doesn't work
Previous:From: Thomas LockhartDate: 2000-04-02 21:06:03
Subject: Re: "list index out of range" in C++ Builder 4

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