| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Dean Gibson (DB Administrator)" <postgresql4(at)ultimeth(dot)com> |
| Cc: | pgsql-sql <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: What does "merge-joinable join conditions" mean ???? |
| Date: | 2006-01-15 23:21:53 |
| Message-ID: | 24299.1137367313@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
"Dean Gibson (DB Administrator)" <postgresql4(at)ultimeth(dot)com> writes:
> SELECT count(*) FROM "GenAppExtra" FULL JOIN "GeoRestrict" ON callsign
> ~ pattern WHERE region_id = 4 OR geo_region = 4;
> If either of the "region_id = 4" (a field in the right-hand table) or
> "geo_region = 4" (a field in the left-hand table) are removed, the
> SELECT functions (does not give an error message),
Really? The FULL JOIN condition using ~ is the source of the failure,
and I'd be quite surprised if changing WHERE makes it work.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Gibson (DB Administrator) | 2006-01-15 23:31:40 | Re: What does "merge-joinable join conditions" mean ???? |
| Previous Message | Dean Gibson (DB Administrator) | 2006-01-15 22:28:08 | Re: What does "merge-joinable join conditions" mean ???? |