From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: Darryl M. Wolski <drwolski@sympatico.ca>
Cc: pgsql-sql@postgresql.org
Subject: Re: nested inner join help
Date: Mon, 14 Jan 2002 18:25:37 -0500
Message-ID: <20144.1011050737@sss.pgh.pa.us> (raw)
In-Reply-To: <web-601184@davinci.ethosmedia.com>
References: <web-601184@davinci.ethosmedia.com>
"Josh Berkus" <josh@agliodbs.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com, drwolski@sympatico.ca
Subject: Re: nested inner join help
In-Reply-To: <20144.1011050737@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox