Received: from golem.jpl.nasa.gov (IDENT:postfix@hectic-1.jpl.nasa.gov [128.149.68.203]) by hub.org (8.9.3/8.9.3) with ESMTP id WAA94003; Tue, 30 May 2000 22:04:43 -0400 (EDT) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (localhost.localdomain [127.0.0.1]) by golem.jpl.nasa.gov (Postfix) with ESMTP id 038ED6EE9; Wed, 31 May 2000 02:04:12 +0000 (UTC) Message-ID: <3934731C.C2D35105@alumni.caltech.edu> Date: Wed, 31 May 2000 02:04:12 +0000 From: Thomas Lockhart Organization: Yes X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14-15mdksmp i686) X-Accept-Language: en MIME-Version: 1.0 To: Tom Lane Cc: Peter Eisentraut , Joseph Shraibman , "pgsql-sql@postgresql.org" , pgsql-hackers@postgreSQL.org Subject: Re: [HACKERS] Re: aliases break my query References: <2392.959358366@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200005/214 > At one time Bruce had made some patches to emit informative notice > messages about implicit FROM entries, but that got turned off again > for reasons that I forget... It was triggered with common cases from the "outer join" syntax. It took a while to track down since it was introduced while I was working on the syntax feature :( If it *really* needs to be put back in, then we should do so with a flag so we can disable the warning at compile time, run time, and/or in the outer join parser area. But imho sprinkling the parser with warnings for allowed syntax is heading the wrong direction. If it is legal, allow it. If it is illegal, disallow it. If it is confusing for some, but works fine for others, it shouldn't become "sort of legal" with a warning. - Thomas