| From: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Oleg Lebedev <olebedev(at)waterford(dot)org> |
| Cc: | Postgres SQL Mailing List <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: sequential joins |
| Date: | 2002-03-01 23:13:31 |
| Message-ID: | web-814403@davinci.ethosmedia.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/plain | 2 bytes |
| unknown_filename | text/plain | 2 bytes |
| unknown_filename | text/plain | 2 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-03-01 23:43:16 | Re: sequential joins |
| Previous Message | Oleg Lebedev | 2002-03-01 22:46:41 | Re: sequential joins |