Syntax-only is a deliberate boundary
The validator does not open a connection, inspect a catalog, or ask a remote service. Unknown tables and unavailable functions therefore remain unresolved.
Parse one explicit SQL dialect and report syntax status, statement count, and statement types.
Inputs stay in this browser tab. Parser-heavy work uses a tighter 256 KiB safety cap.
No result is placed in a URL, account, API, or remote log.
Bounded, explicit-dialect processing
A valid parse proves only that the selected grammar accepts the text. Tables, columns, permissions, constraints, extensions, data types, and runtime behavior require the target database.
The validator does not open a connection, inspect a catalog, or ask a remote service. Unknown tables and unavailable functions therefore remain unresolved.
Malformed SQL returns a local diagnostic while the original source stays in the editor.
The parser runs locally under byte, statement, AST-node, depth, row, column, diagnostic, and output limits. It never connects to a database or resolves files and URLs.