On Thu, Mar 24, 2011 at 5:42 AM, Harald Mueller <[email protected]> wrote:
> Ad c. Right now, my code has an if at the end where it essentially says "if I
> did not produce an outer join, then don't do anything different" = "use table
> joins."
> I did this to not change the behavior in all cases that already work
> correctly - which could be important for applications that have tuned their
> indices to query plans resulting from the table joins. Personally, I'd prefer
> to have "the one and only" join method - i.e., always create inner and outer
> joins, never table joins.
Just off the top of my head, I tend to agree. I think it's better to
express the intention (inner join) in a consistent way. I imagine
databases would on average perform better this way anyways.
Patrick Earl