SQL formatting and indentation
Formatting a SQL query means rewriting the same statement across several indented lines, one per clause, without changing what it does, and the result is only trustworthy when the formatter understands exactly where a string ends and a comment begins.
Each uppercase keyword (the default option) starts its own line, and the condition after AND lines up with the previous WHERE condition.
Backticks are MySQL's way of quoting a name that collides with a reserved word, here "order"; the dialect needs to be MySQL or MariaDB for that quoting to be recognized.
Instead of a trailing comma at the end of each line (the default style), this option moves the comma to the start of the next line, a style common in SQL diff reviews.
The formatter supports standard SQL, MySQL, MariaDB, PostgreSQL, SQLite, BigQuery, SQL Server (T-SQL) and Oracle (PL/SQL). The chosen dialect also decides how the text is read: MySQL backticks, SQL Server brackets, PostgreSQL double quotes as identifiers and dollar-quoted blocks (PostgreSQL's $$) are recognized and preserved.
Because each database engine quotes identifiers differently: backticks in MySQL, brackets in SQL Server, double-dollar in PostgreSQL. The formatter uses the chosen dialect to know where a quoted identifier starts and ends, and picking the wrong dialect can make that quoting get read as plain code.
No. The tokenizer identifies where every string literal, line comment, or block comment starts and ends before applying any indentation, so the text content inside them reaches the final result intact, byte for byte.
Trailing comma (the default) puts the comma at the end of each column line; leading comma moves the comma to the start of the following line. The result runs identically in the database, it is purely a visual preference that makes it easier to see what changed in a version-control diff.
The tokenizer never throws an error on its own: an unterminated string or comment is read through to the end of the text and flagged internally as unterminated, so the result degrades back to the original text instead of crashing or truncating content.
WITH
ativos AS (
SELECT
id,
name
FROM
users
WHERE
status = 'active'
)
SELECT
a.id,
a.name,
count(o.id) AS orders,
sum(o.total) AS revenue
FROM
ativos a
LEFT JOIN orders o ON o.user_id = a.id
WHERE
o.created_at > '2024-01-01'
GROUP BY
a.id,
a.name
HAVING
count(o.id) > 3
ORDER BY
revenue DESC
LIMIT
10;WITH
ativos AS (
SELECT
id,
name
FROM
users
WHERE
status = 'active'
)
SELECT
a.id,
a.name,
count(o.id) AS orders,
sum(o.total) AS revenue
FROM
ativos a
LEFT JOIN orders o ON o.user_id = a.id
WHERE
o.created_at > '2024-01-01'
GROUP BY
a.id,
a.name
HAVING
count(o.id) > 3
ORDER BY
revenue DESC
LIMIT
10;Everything happens in your browser. No query and no file is sent to any server.