PHWinfo - Afficher un message - difference between explicit inner join and implicit

01/04/2008, 16h07

>> Technically no, but it's a good idea to make it a habit to use the explicit inner join. It is considered the standard nowadays, <<

Not when I was on the Standards Committee; did you join later than
me?

>> is easier to read and debug, <<

NO, it isn't; have you seen any of the human factors research? The ON
clauses can be spread so far from the matching tables debugging time
increases. Multiple parameter predicates like BETWEEN and IN are
split and their higher level meaning is lost.

But it looks like ACCESS and has a nice binary operator feel that
procedural programmers like.

>> and is consistent with the OUTER JOIN syntax. <<

Yes, that is the reason it exists.

01/04/2008, 16h07	#7
--CELKO-- Messages: n/a Hébergeur:	Re: difference between explicit inner join and implicit >> Technically no, but it's a good idea to make it a habit to use the explicit inner join. It is considered the standard nowadays, << Not when I was on the Standards Committee; did you join later than me? >> is easier to read and debug, << NO, it isn't; have you seen any of the human factors research? The ON clauses can be spread so far from the matching tables debugging time increases. Multiple parameter predicates like BETWEEN and IN are split and their higher level meaning is lost. But it looks like ACCESS and has a nice binary operator feel that procedural programmers like. >> and is consistent with the OUTER JOIN syntax. << Yes, that is the reason it exists.