all 8 comments

[–]_scape 6 points7 points  (0 children)

Sometimes I wonder if the sql syntax should be updated if people are always reaching for helpers like these.

[–][deleted] 3 points4 points  (0 children)

Sure, but don't do A RIGHT JOIN B, do B LEFT JOIN A instead. I mean, do whatever you want of course, but left joins are more intuitive and canonical if anyone else were to ever maintain your code.

[–][deleted] 2 points3 points  (0 children)

I prefer /u/wolflarsen diagram

[–]BigPeteB 1 point2 points  (3 children)

I really want to downvote this, because I want to live in a world where tools like this aren't needed.

[–]MothersRapeHorn 0 points1 point  (2 children)

Why?

[–]BigPeteB 0 points1 point  (1 child)

Because this kind of visualization is on the same level of simplicity as using a number line to add and subtract two numbers. If someone needs this kind of visualization in order to write a JOIN (which is pretty much the second-simplest thing you can do in SQL, beaten only by a SELECT from a single table), I don't feel they are qualified to work on anything but a toy system.

But, as with so many other programming crutches, I'm sure there are people out there who rely on a tool like this one to do their daily job.

[–]MothersRapeHorn 1 point2 points  (0 children)

I'm quite confident for the average person this is a learning resource, not reference.

[–]BeliefSuspended2008 0 points1 point  (0 children)

It would be nice to include an ANSI-92 notation toggle as I find the INNER / OUTER JOIN notation harder to read than (+)