| From: | John Taylor <postgres(at)jtresponse(dot)co(dot)uk> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, John Taylor <postgres(at)jtresponse(dot)co(dot)uk> |
| Cc: | "Joel Burton" <joel(at)joelburton(dot)com>, "PgSQL Novice ML" <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: Full Outer Joins |
| Date: | 2002-05-27 19:05:07 |
| Message-ID: | 0205272005070B.01493@splash.hq.jtresponse.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Monday 27 May 2002 20:02, Tom Lane wrote:
>
> If that actually has the behavior you want, then that's the way you
> write it. Placing restrictions inside an outer join is not semantically
> the same as placing them outside (at the WHERE clause), so it wasn't
> clear to me exactly what you wanted.
>
Ah, that explains why I couldn't figure it out.
I think I need to move on from my current Postgres Bible, it stops short of
full outer joins :-(
Thanks
JohnT
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sharon Cowling | 2002-05-28 06:27:45 | Re: Copy Comand question |
| Previous Message | Tom Lane | 2002-05-27 19:02:36 | Re: Full Outer Joins |