Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0ENPcV71449 for ; Mon, 14 Jan 2002 18:25:38 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g0ENPbg20147; Mon, 14 Jan 2002 18:25:37 -0500 (EST) To: "Josh Berkus" cc: "Darryl M. Wolski" , pgsql-sql@postgresql.org Subject: Re: nested inner join help In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Mon, 14 Jan 2002 13:30:36 -0800" Date: Mon, 14 Jan 2002 18:25:37 -0500 Message-ID: <20144.1011050737@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200201/153 X-Sequence-Number: 6239 "Josh Berkus" writes: > One significant MSAccess <==> Postgres conflict is that Postgres assumes that > parens in the FROM clause represent subselects (I think), 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. regards, tom lane