• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Are Venn diagrams bad for explaining SQL Joins ?

Ranch Hand
Posts: 143
IntelliJ IDE Eclipse IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Apparently, they are bad because JOINS are not really set operations, but are actually a cartesian product - https://blog.jooq.org/2016/07/05/say-no-to-venn-diagrams-when-explaining-joins/.
IMO, that might be technically correct. But, to me, the venn diagrams are easier to understand and remember compared to cross product diagrams. I don't know why venn feels easier though. Maybe because venn is the first thing I learned and got used to it, or maybe it is really easy because the diagrams are simple. IMO, what matters is whether something helps you to understand things easily and correctly. Does not matter if it is "technically incorrect".

What do you think ?

Posts: 15892
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think that it's valid to whatever extent the analogy helps you improve your understanding. If you don't know where the analogy ends and ceases to be applicable, then you might have a problem where it starts to mislead rather than clarify.
    Bookmark Topic Watch Topic
  • New Topic