Formateo SQL / IndentaciónCódigo
Why is SQL code formatting crucial?
Aligns clauses, keywords, and predicates cleanly, speeding up developer comprehension and mitigating logical bugs in multi-table joins.
DEVELOPMENT & DATABASES
SQL Formatter & SQL Minifier
Beautify, indent, minify, and lint SQL queries for PostgreSQL, MySQL, SQLite, and SQL Server instantly and 100% in your browser.
100% local execution — No SQL queries leave your browser
Raw SQL (Input)786 chars · 1 lines
Query Metrics & Best Practices Linter
Code Lines
01 prev
Chars / Compression
0-100%
Keywords Detected
23
Detected Tables
5
Referenced tables:orderscustomersorder_itemsproductscategories
Consulta Sintácticamente Validada
No se detectaron problemas de seguridad básicos ni discrepancias en delimitadores.
SQL Lexical Analysis & AST
The formatting process breaks the query into a token stream (keywords, operators, literals, and delimited identifiers). It reconstructs the logical hierarchy by grouping major clauses (SELECT, FROM, WHERE, JOIN) and recursively indenting subqueries.
Structure: Main Clause → Columns / Expressions → Data Sources (JOINs) → Filters (WHERE / HAVING) → Ordering.
ANSI SQL vs Engine Dialects
Although ANSI SQL establishes the baseline standard, each RDBMS provides distinct features: PostgreSQL stands out with JSONB and RETURNING; MySQL with backticks and LIMIT offset; T-SQL with brackets [table] and TOP; SQLite with its serverless embedded architecture.
Portability: Adhere to ANSI syntax when possible to simplify migrations between database engines.
CTEs (WITH) vs Subqueries
Common Table Expressions (WITH ...) turn deeply nested queries into readable, top-to-bottom sequential steps. In PostgreSQL 12+ and MySQL 8+, query optimizers automatically choose whether to materialize or inline each CTE for optimal performance.
Best Practice: Prefer descriptively named CTEs instead of deeply nested subqueries inside the FROM clause.
Minification in Production & APIs
Minification strips redundant whitespace, line breaks, and comments before embedding SQL queries into source code strings (Node.js, Python, Go) or sending them over microservice network sockets, decreasing byte payloads and parser overhead.
Savings: Reduces massive SQL migration scripts or DDL payloads by up to 40-60%.
1. SyntaxError: Single vs Double Quotes
Database engine rejects query with syntax error when parsing string literals or identifiers.
Quick Fix
Always use single quotes 'text' for literal strings, and double quotes "column" or backticks `col` only for column/table identifiers with spaces or reserved words.
Technical Insight
In ANSI SQL, single quotes define string literals ('admin'), whereas double quotes delimit schema identifiers ("User Role"). In MySQL, double quotes default to strings unless ANSI_QUOTES mode is enabled.
2. Error: Column 'id' in field list is ambiguous
The query fails in JOIN statements because multiple tables share an identical column name.
Quick Fix
Prefix each column reference with its corresponding table alias (e.g. u.id instead of just id).
Technical Insight
The query planner cannot resolve which table in the Cartesian product owns the unqualified attribute. Assigning concise aliases (FROM users u JOIN orders o ON ...) and qualifying all column references eliminates ambiguity.
3. HAVING Clause Error Without GROUP BY or Aggregation
Database engine throws errors or warnings when attempting to filter individual rows using HAVING.
Quick Fix
Change HAVING to WHERE if filtering normal row attributes. Use HAVING strictly for aggregated metrics like COUNT() > 5 or SUM() >= 100.
Technical Insight
SQL execution order runs: FROM → JOIN → WHERE (filters individual rows) → GROUP BY → HAVING (filters aggregated groups) → SELECT → ORDER BY. Using HAVING for non-aggregate conditions forces inefficient late filtering.
4. Accidental UPDATE / DELETE Without WHERE Clause
Severe risk of modifying or purging 100% of rows in a production table.
Quick Fix
Run a SELECT * FROM table WHERE ... first to inspect matching rows before transforming it into UPDATE or DELETE.
Technical Insight
Always wrap mutating DML queries in transactions: BEGIN; UPDATE ...; SELECT verification; and run COMMIT only after verifying, or ROLLBACK on mistake. In MySQL, enable sql_safe_updates = 1.
History & Trademarks#1
Why SEQUEL became SQL?
In 1974, IBM researchers Donald Chamberlin and Raymond Boyce created 'SEQUEL' (Structured English QUEry Language). They abbreviated it to 'SQL' after discovering that SEQUEL was already a registered trademark of the British Hawker Siddeley aircraft company.
Mathematical Logic#2
The Three-Valued Logic of NULL
Edgar F. Codd introduced NULL into the relational model based on Jan Łukasiewicz's three-valued logic. Consequently, NULL = NULL evaluates to UNKNOWN rather than TRUE, requiring specialized operators like IS NULL or IS NOT DISTINCT FROM.
Evolution & Standards#3
The Standard Still Growing Since 1986
The ANSI/ISO SQL standard has evolved for nearly four decades across 9 major revisions (SQL-86, SQL-89, SQL-92, SQL:1999, SQL:2003 with XML, SQL:2008, SQL:2011 with temporal tables, SQL:2016 with JSON, and SQL:2023 with Property Graph Queries PGQ).
Technology Record#4
SQLite: The Most Deployed Software in Human History
Created in 2000 by D. Richard Hipp aboard a US Navy guided missile destroyer, SQLite is the embedded SQL engine powering every iPhone, Android device, web browser, messaging app, and modern airliner, with over 1 trillion (10¹²) active databases worldwide.
SQL Syntax & Execution Plans Glossary
Learn the fundamental concepts, protocols, and technical terminology of this tool.
Normalización de Mayúsculas (Keywords)Estilo
Why are SQL keywords written in uppercase?
A universal readability convention differentiating built-in engine commands from arbitrary database schema identifiers and application variables.
Plan de Ejecución (Query Plan)Rendimiento
What is an SQL Query Execution Plan?
The procedural roadmap chosen by the database cost optimizer to retrieve records, choosing between sequential scans or index lookups.
Inyección SQL (SQLi)Seguridad
What is SQL Injection (SQLi)?
A severe exploit where unsanitized user inputs mutate query execution logic; mitigated via parameterized prepared statements.