SQL Query Visualizer Guide: How to Read the Diagram

The SQL Query Visualizer takes a pasted SELECT query and produces two things: a join diagram showing which tables connect to which and how, and a numbered list showing the order your database actually evaluates the query's clauses. This guide walks through a real 3-table example so you know exactly what each part of the output is telling you.

A Worked Example

Paste a query like this one:

SELECT o.id, c.name, p.product_name
FROM orders o
JOIN customers c ON o.customer_id = c.id
LEFT JOIN products p ON o.product_id = p.id
WHERE o.status = 'shipped'
ORDER BY o.id DESC
LIMIT 10;

The tool parses this with a real SQL parser (not keyword pattern-matching), so it correctly identifies three tables — orders aliased o, customers aliased c, and products aliased p — and the exact condition each JOIN uses to connect them.

Reading the Join Diagram

The diagram lays the three tables out left to right in the order they're joined, with a colored badge between each pair naming the join type and the ON condition underneath:

• orders → JOIN (ON o.customer_id = c.id) → customers
• customers → LEFT JOIN (ON o.product_id = p.id) → products

Each join type gets its own color, matching the palette used in the SQL JOIN types guide — INNER teal, LEFT blue, RIGHT orange, FULL purple — so once you've read that guide, the diagram's colors are already familiar. Seeing "LEFT JOIN" highlighted in blue here is a quick visual confirmation that unmatched orders (ones with no product) are still kept, not silently dropped.

Reading the Execution Order List

Below the diagram, a numbered list shows the clauses in the order the database logically evaluates them — not the order you typed them:

1. FROM orders o
2. JOIN customers c ON o.customer_id = c.id
3. LEFT JOIN products p ON o.product_id = p.id
4. WHERE o.status = 'shipped'
5. SELECT o.id, c.name, p.product_name
6. ORDER BY o.id DESC
7. LIMIT 10

Notice WHERE runs before SELECT, even though you wrote SELECT first — the filter on o.status happens on raw joined rows, before the final column list is even computed. For the full reasoning behind why SQL executes in this order, see how SQL execution order works.

What an Unlabeled Join Edge Means

If you paste a query where a JOIN is missing its ON condition — often from a typo or a copy-paste mistake — the diagram still draws the connection between the two tables, but with no condition label underneath it:

SELECT c.name, o.id
FROM customers c
JOIN orders o;  -- missing ON condition

An unlabeled edge is a warning sign: without an ON condition, this becomes a cross join — every customer paired with every order, not the intended one-to-many relationship. On real tables with thousands of rows, that produces a result set orders of magnitude larger than intended. Seeing the missing label in the diagram is often easier to catch than spotting it in the raw SQL text.

Frequently Asked Questions