× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Luis,

Thanks man, you made my day. *Normally* I would embrace newer technologies and syntax whole heartedly (hey! I am learning Ruby and Rails right now). But I also don't toss old stuff just because there is new stuff to replace it. The brain cells I have that survived the 70's are limited, so I don't use them unless I *have* to. :-)

I knew that the addition of the "join" was "relatively" new and Joe's post at least gave me no immediate reason to stop using "where" (although I do agree that "join" is more self documenting and therefore I AM changing my SQL habits [using a few more brain cells.....]).

Old dogs DO learn new tricks but only if we *need* to....

Pete

Luis Colorado wrote:
Rob wrote:

But, me, I'd avoid the where clause for a couple of reasons. One, it flags you as someone who only learned SQL by taking Query/400 and doing a RTVQMQRY against it. Two, you can do stuff with JOIN that Query/400 explains to you, but warns you with ANZQMQRY that they won't export correctly with RTVQMQRY - like left outer join, (or as Query calls it:
FYI... the "JOIN" keyword is a relatively new guy. When I learned DB2 SQL queries from the classic Date's database book in the 80's, "JOIN" was not there yet.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.