Typed SQL
The SQL screen: a single SELECT with autocomplete, its parsing and compilation, and the limit and grouping rules.
The SQL screen accepts a single SELECT in your database’s dialect,
with schema-aware autocomplete and a schema picker. With a schema selected, FROM needs no prefix. Ctrl/Cmd+Enter runs the statement. Ctrl/Cmd+Space completes.
With no saved connection selected, the screen shows only the Choose a database to query prompt and an Open Connections action.
Parsing and compilation
Typed SQL is parsed into the same structured, parameter-bound query the builder produces. The database receives the compiled query, not the text you typed. Row limits, risk scoring, and confirmation follow the same rules; see Limits & risk model.
SELECT * expands to the table's columns. Compiled result columns are named table__column. The grid shows the column name and qualifies it with the table when
two columns share a name. A near-miss keyword suggests the intended word, so FORM is reported as did you mean FROM?
Date literals use YYYY-MM-DD. Timestamps accept a date, a space-separated value
such as 2024-01-01 09:30[:SS], or YYYY-MM-DDTHH:MM[:SS]. A date alone
means midnight. Timestamps with a UTC offset are rejected.
Write LIMIT on PostgreSQL and MySQL, TOP on SQL Server, FETCH FIRST on Oracle and Db2. A positive limit is kept up to the 32-bit integer maximum.
Omitting it is the same as the builder's ALL: no row limit is emitted. The sample still stops at 10
MiB encoded, and the query timeout applies.
DISTINCT is accepted. With distinct rows, every sort column has to be in the select list.
When grouping is on, every selected column and every sort column has to appear in the group.