From: | Tim Uckun <timuckun(at)gmail(dot)com> |
---|---|
To: | Tony Theodore <tony(dot)theodore(at)gmail(dot)com> |
Cc: | Alban Hertroys <haramrae(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Why is this a cross join? |
Date: | 2013-02-17 22:09:55 |
Message-ID: | CAGuHJrMD6inC5mqiGg1Jh2R7dBJbM6rqW+q3UeYHNi68+oT6ng@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>
> In some way, every join is a cross join, with the results filtered according to the specificity of the join conditions. In this case:
>
> inner join model_configurations mc on left(crm.customer_class, 6) = left(mc.sap_code,6)
>
> "customer_class" sounds like a fairly generic sort of field, so you'd expect many matches. Truncating the fields is likely to make this even less specific, returning more results.
>
I guess I am not explaining it properly..
Say I created new columns on both tables called "first_6" and
populated them with the substrings. If I did a inner join or a left
join on those fields would I still get a cross join?
inner join model_configurations mc on mc.first_6 = crm.first_6
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2013-02-17 22:17:05 | Re: Why is this a cross join? |
Previous Message | Tony Theodore | 2013-02-17 21:26:24 | Re: Why is this a cross join? |