Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • There are two reasons I have encountered for implicit joins. Some systems don't support the synrax. SQL::Statement is the one I have encountered.

    Also, some databases don't optimize as well with explicit joins. Until recently, PostgreSQL would not reorder joins and this limited how well the optimizer worked. The most recent version of PostgreSQL fixed this problem. But OUTER JOINs can't be reordered without potentially changing the results.

    I much prefer explicit joins. I think they the queries mu

  • This is actually how I teach SQL, insisting on the explicit syntax for clarity (and sometimes correctness, as you point out in your example). See sql_tutorial.pdf [virginia.edu] for the material I use. I absolutely forbid the use of commas as join operators.

    Unfortunately, Oracle has no support for standard SQL, using it's own odd syntax for joins (comma-separated tables, and where clauses with optional "+" symbols to denote outer join directions). Ugly.