Functions

NYXDB ships a generated per-function reference built from the engine manifest. The live registry—not a static marketing count—is authoritative for the revision you run.

Discover the live inventory

SHOW FUNCTIONS;
SHOW FUNCTIONS LIKE 'json%';
SHOW FUNCTIONS LIKE '%distance';

There is no system.functions relation in the current engine. Use SHOW FUNCTIONS to confirm availability and spelling before deploying a query that depends on a newly introduced function.

Browse by family

All function families

Generated signatures and descriptions from the engine manifest.

Array

Array construction, search, reduction, and transformation.

Date and time

Parsing, bucketing, arithmetic, and formatting.

JSON

JSON extraction, construction, mutation, and inspection.

Math

Numeric, logarithmic, rounding, and arithmetic functions.

String

Text search, splitting, replacement, and Unicode-aware operations.

Vector

Distance and similarity functions used by vector search.

Window

Window-function signatures and execution requirements.

Exact distinct aggregates and memory

count_distinct, uniq, and uniq_exact all use exact distinct state in the current release. uniq is not a probabilistic estimator today. Their result is therefore deterministic for the same input, but state grows with distinct cardinality rather than total scanned rows.

Native bucket arrays, metadata, replacement peaks, and string arenas participate in the statement operator-memory budget and the process-wide --query-global-exact-memory-bytes counter. Input crosses the native ABI in batches of at most 4,096 rows so a large string scan reaches cancellation and budget checkpoints without first allocating one carrier for every source row.

When either memory envelope is exhausted, the statement fails closed with NYXDB_EXEC_BUDGET_EXCEEDED: ... memory ...; it does not silently approximate, truncate, or return a partial relation. State and global reservations are released before the failure crosses the one-shot boundary. Operators should inspect rows_scanned, peak_memory_bytes, and error in system.query_log before changing the limit. See Query admission and limits.

Binding and compatibility

Functions are resolved by name, argument types, and signature in the binder. Use explicit casts when overload selection would be ambiguous. Compatibility review should cover:

the function's presence and signature in the generated page;
input, return, and null behavior;
determinism under the intended query shape;
aggregate merge/retract and streaming-state requirements; and
the function's presence in SHOW FUNCTIONS on the target release.

Hot-loadable native function modules have an experimental operational and ABI surface. Package only reviewed modules built for the exact deployed ABI, test failure isolation, and avoid making an unpinned external module a required production dependency.