Re: next baby step in SQL: start using join

["Michael Naughton" <mnaughton@xxxxxxxxxxxx>]

I tend to use JOINs -- I guess it's just the way I learned it. I think it
makes it easier when I am combining JOINs (which are actually INNER JOINs)
with OUTER JOINs (as someone else said). Also, I have learned from
experience that I can significantly speed up a query by re-arranging the
order of the JOINs, following the rule of trying to reduce the size of the
result set as quickly as possible as early as possible. (I've also found
that using WITH can speed things up, but that's another story. . .).

I don't know if the optimizer would find the best combination of joins
when just WHEREs are used, but it shouldn't be hard to check: just create
a query where the order of the JOINs really matters and then test various
orders using JOINs and WHEREs. No time today, but I may try this some day.
. . .

midrange-l@xxxxxxxxxxxx writes:
>I find using the JOIN makes
>it more apparent that you are joining files and how you are joining them.
> (vs. using WHERE to do
>the join.)
>
>Comments and advice are welcome & appreciated.
>
>- Dan


Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@xxxxxxxxxxxx