Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id 31288475EA1 for ; Fri, 1 Mar 2002 18:13:35 -0500 (EST) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.2) with HTTP id 814403; Fri, 01 Mar 2002 15:13:31 -0800 From: "Josh Berkus" Subject: Re: sequential joins To: Oleg Lebedev Cc: Postgres SQL Mailing List X-Mailer: CommuniGate Pro Web Mailer v.3.5.2 Date: Fri, 01 Mar 2002 15:13:31 -0800 Message-ID: In-Reply-To: <3C8004D1.40DEF8A1@waterford.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_===814403====davinci.ethosmedia.com===_" X-Archive-Number: 200203/15 X-Sequence-Number: 6897 This is a multi-part MIME message --_===814403====davinci.ethosmedia.com===_ Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Oleg, > the sub-select statement I was using were not for filtering data (in > which > case you can move filtering condition in ON part of the join), but > rather > renaming the column 'username' with the name I need in the current > join > statement. In this case, columns with new names ('artist', > 'designer', > 'programmer') would be appended to the overall query result and can > be > selected by top-level select statement. > This looks like a very clumsy way to do what I need. > Any ideas? No, now I'm confused. Can you explain better what you are trying to achieve as a result? -Josh --_===814403====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Transfer-Encoding: base64 DQo= --_===814403====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Transfer-Encoding: base64 DQo= --_===814403====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Transfer-Encoding: base64 DQo= --_===814403====davinci.ethosmedia.com===_--