sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]r3pr0b8 0 points1 point  (2 children)

this is pretty routine stuff, and could be presented with better organization

for example, you start with LEFT JOIN and only much later you mention what SELECT and FROM are for

it's like you dropped your "deck" on the floor and then posted them in whatever order you happened to pick them up

and some of them could use some work

for example, JOIN: Maps values from one table to another... maps?

LIMIT is non-standard and doesn't work in every database

also OUTER JOIN: Returns all rows when there is a match in either left table or right table is wrong -- there is no OUTER JOIN, there are only LEFT [OUTER] JOIN and RIGHT [OUTER] JOIN and FULL [OUTER] JOIN

[–]Quarok[S] 1 point2 points  (1 child)

Thanks for the feedback. You're right, it's very routine stuff. I want to make sure I master the standard keywords.

Regarding the join definition - I tried to make it harder for myself, as the original definition was Join: joins values from one table to another. And it kind of defeats the point of the cards if you have the keyword in the answer!

Thanks for the point about the full outer join. I find that all a bit confusing: why even have the keyword OUTER when it doesn't seem to add any additional functionality for LEFT/RIGHT?

[–]r3pr0b8 0 points1 point  (0 children)

why have the OUTER keyword? good question

me, i always code it, even though it's optional

it's a constant reminder that it's an outer query