Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0F11dV02311 for ; Mon, 14 Jan 2002 20:01:40 -0500 (EST) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.2) with HTTP id 601476; Mon, 14 Jan 2002 17:01:40 -0800 From: "Josh Berkus" Subject: Re: nested inner join help To: Tom Lane , "Josh Berkus" Cc: "Darryl M. Wolski" , pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.5.2 Date: Mon, 14 Jan 2002 17:01:40 -0800 Message-ID: In-Reply-To: <20144.1011050737@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200201/155 X-Sequence-Number: 6241 Tom, > Huh? Parenthesizing JOINs is perfectly valid, and I think it's good > style too in complex cases. See the nearby "SQL Joins" thread for > an example of a query that's quite unreadable without 'em. Aha. I see. Of course, the OUTER JOINs here sort of require parens. So, Darryl, you do want to use parens some of time. Just to make it harder for you to decide. However, I would assert that in your example query they are not necessary and actually make the syntax more difficult. -Josh Berkus ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco