SQL Joins… But Make Them Tarot

SQL joins are usually explained with Venn diagrams, charts, or code snippets. And then I had this pretty cool idea.

Because guess what… analysts have fun too and data doesn’t have to be boring *wink-wink*. So —

What if we gave sql joins mystical archetypes instead?

I designed a tarot-inspired deck where each join type becomes a card — complete with symbols, archetypes, and short fortunes.

I included all join types (Inner, Left, Right, Outer, Cross, Self, Natural, Semi, and Anti) to make the set feel more complete, even if most people only cover the most common ones.

DISCLAIMER 🔮

Not every database system supports all join types the same way. Think of them like tarot archetypes: some are the classic cards you’ll always pull, some are special but still standard, and a few are rare but powerful when you know them.

The Core 4 (the joins everyone learns first):

• INNER JOIN
• LEFT JOIN (LEFT OUTER)
• RIGHT JOIN (RIGHT OUTER)
• FULL OUTER JOIN
  These are the backbone of SQL joins — standard across SQL Server, MySQL, PostgreSQL, Oracle, and almost every tutorial or bootcamp.

Standard but less commonly used:

• CROSS JOIN – Supported everywhere, but less commonly taught because it returns every possible pairing (which can blow up row counts fast).
• SELF JOIN – Also standard, but often taught later. It’s just a table joining to itself, like looking in a mirror.

Natural Join (The Magician):

• Supported in Oracle, PostgreSQL, and MySQL, but not SQL Server (SSMS).
• It auto-matches columns with the same name — which feels magical ✨ but can be dangerous in production since it might pull in new columns you didn’t expect. That’s why it’s rarely used or covered in tutorials.

The “Rare Cards” (not always explicit keywords):

• SEMI JOIN and ANTI JOIN
  • In PostgreSQL and Oracle, they exist as recognized operations.
  • In SQL Server and MySQL, they’re simulated with subqueries (EXISTS / NOT EXISTS or IN / NOT IN).

Why I included them all:
Most people only ever see the “core 4” (and maybe cross join). But including Self, Natural, Semi, and Anti shows the full spread of how SQL handles matches and non-matches. That’s why my Tarot deck has 9 archetypes instead of 4 or 5.

Are you ready?

The SQL Tarot Deck

inner join – the matchmaker

Only rows that match on both sides are kept. Harmony, balance, and true pairs.

Left Join – The Caretaker

All rows from the left remain, even if the right gives nothing back. Loyalty and nurture.

right join – the ally

All rows from the right remain, with the left joining where it can. Steadfast support.

full outer join – the world

All rows from both tables are included. Matches and loners alike find a place in the whole.

cross join – the trickster

Every row pairs with every other. Endless possibilities, but beware of chaos.

SELF JOIN – THE MIRROR

A table reflects on itself, revealing hidden patterns within.

natural join – the magician

Automatically connects matching columns — a shortcut that feels like magic.

ANTI JOIN – THE HERMIT

Only rows without matches are shown. Solitude and independence define this path.

SEMI JOIN – THE SEER

Rows are revealed if they exist in another set, but details remain veiled.

pretty cool right?

WHAT’S NEXT

It doesn’t end here, my fellow analysts.

COMING NEXT

• A full overview of all the joins and their syntax using Tarot inspired tables.

• Which SQL Join Are You? — an interactive quiz to reveal your archetype.

AND AFTER THAT…

• Tarot Reader in Python (with ASCII art cards)

So tell me… which SQL Tarot card speaks to you?