The REPL will not submit a SQL statement

SQL input continues until the statement ends with ;.

SELECT 1;

Dot commands such as .tables and .schema do not use semicolons.

unknown table

Register the table in the current REPL session:

.open events ./events.vortex

Then confirm it exists:

.tables

Tables are session-local. Restarting the REPL clears in-memory tables and file registrations.

expected one statement

The REPL accepts one SQL statement at a time. End each SQL statement with ;. Do not submit two SQL statements in the same input.

unsupported SQL feature

The parser may recognize more SQL than the current binder can execute. Check the SQL support matrix, then simplify the query or split the workflow into supported steps.

Common causes:

• joins
• CTEs
• derived tables
• DISTINCT
• window functions
• named function arguments
• INSERT ... SELECT

unknown SPQL function

Scalar and aggregate functions resolve through the engine callable catalog. Use fully qualified names such as spql.add when in doubt.

For table and source functions, query the registered catalogs:

SELECT function_set, parameters, summary
FROM spql.meta.table_functions();
 
SELECT function_set, parameters, summary
FROM spql.meta.source_functions();

.open fails for a path

.open requires at least one Vortex file path:

.open events ./events.vortex

The REPL does not expand shell globs. Pass explicit paths or paste an expanded command.

Text inserts fail with NULL text values are not supported

The current in-memory table materializer does not support NULL in text columns. Use a non-null string value for TEXT, VARCHAR, STRING, and related text columns.

Empty or truncated output

--max-rows limits the REPL preview size by collecting at most one extra row for display. Use --max-columns 0 to print all columns and --max-cell-width 0 to avoid text truncation. Add an explicit SQL ORDER BY ... LIMIT when you need a deterministic limited result.