| From: | Sim Zacks <sim(at)compulab(dot)co(dot)il> | 
|---|---|
| To: | pgsql-general(at)postgresql(dot)org | 
| Subject: | Re: join condition against where with coalesce | 
| Date: | 2006-11-12 09:01:09 | 
| Message-ID: | ej6ntt$1ut8$1@news.hub.org | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
I figured out my problem.
Table1 and Table2 have matches for every pk,fk just not on typeid=14,
therefore when I join on just the pk,fk and do a where looking for null, it
doesn't find any rows that qualify.
Doesn't help me solve my problem, but at least I know where I'm at.
Sim
Sim Zacks wrote:
> Should there be any difference between:
> 
> select * from table1 a left join table2 b on a.pk=b.fk and b.typeid=14
> and
> select * from table1 a left join table2 b on a.pk=b.fk
> where coalesce(b.typeid,14)=14
> 
> The reason I need to use the coalesce is because my goal is to do it 
> with a full join and can't use
> the and condition because it is not merge-joinable.
> 
> My test with the left join showed me that with the where it doesn't give 
> any results, while I would expect it to give me all the results in the 
> first table.
> 
> Any thoughts?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cabbar Duzayak | 2006-11-12 10:20:43 | Pushing the Limits | 
| Previous Message | Sim Zacks | 2006-11-12 08:29:02 | join condition against where with coalesce |