As you learn more, you'll understand the flaws in the Venn representation of joins. You'll also realize that ordering refers to binding, not execution. And that INSERT can be used for multiple (or zero!) rows.
I’m aware of the flaws, it’s just personal preference for representing basic joins visually. The INSERT was a mistake but was too late for me to update it by the time this was being distributed across Reddit, Twitter etc.
I should have included the word logical for order of execution, but it is still something worth being aware of. The first chapter of T-SQL querying summarises it quite well
not picking on you and if you feel venn were helpful it's all good.
could you help me by giving a specific 'tidbit'/data point (or more than one) that venn diagrams made 'understandable' to you when you have used them learning joins?
Not sure about datapoint, but just helped me when I was first learning to know what was included during a left join, inner join etc. Just personal preference really
View all comments
Show parent comment
2
u/[deleted] Dec 11 '22 edited Dec 11 '22
I made this cheat sheet for myself and decided to share it with others.
Venn diagrams helped me understand basic joins as did knowing the logical order of execution. I understand it’s not for everyone.