From: Bruce Momjian <maillist@candle.pha.pa.us>
Message-Id: <199805151351.JAA10949@candle.pha.pa.us>
Subject: Re: [HACKERS] Re: [INTERFACES] Group/Order by not in target - Was
	[NEW ODBC DRIVER]
To: sferac@bo.nettuno.it (Jose' Soares Da Silva)
Date: Fri, 15 May 1998 09:51:07 -0400 (EDT)
Cc: hackers@postgreSQL.org (PostgreSQL-development)
In-Reply-To: <Pine.LNX.3.96.980515132342.570A-100000@proxy.bazzanese.com> from
	"Jose' Soares Da Silva" at May 15, 98 01:34:04 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

> 
> On Mon, 11 May 1998, David Hartwig wrote:
> 
>  
> > It is not very difficult to produce this problem in MS Access 97;  I
> > expect my users to beat me up pretty good on this issue.  Thus, I plan to
> > look into making the fix in the backend myself.  Conceptually it does not
> > seem too difficult.
> > 
> > 1. Add a hidden attribute to the target node structure.
> > 
> > 2. Modify the parser/analyzer to add any attributes in the GROUP/ORDER BY
> > clause that are missing from the target list, to the target list with the
> > hidden attribute set.
> This would be a great enhancement! 
> SQL92 specifies that columns in the ORDER BY must appear in the
> SELECT clause, but this limitation has no sense, indeed many databases
> already implement this enhancement.
> Go for it!

There already is code in the backend for Junk fields to be removed.  Not
sure what it does, though.
-- 
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)