ANSI SQL Compliance

ANSI SQLTime TravelNative Extensions

Stable On by default · production-ready

What it is

AetheriusDB exposes a standard ANSI SQL surface: SELECT, JOIN, recursive WITH, window functions, GROUP BY with ROLLUP / CUBE, and set operations. Your existing BI tools, ORMs, dashboards, and ad-hoc psql queries work without rewrites against the PostgreSQL-compatible wire endpoint.

On top of that standard surface, AetheriusDB layers a small set of native extensions that surface its underlying capabilities — time-travel, storage residency policies, and declarative quality checks — directly in DDL. You don’t manage these through sidecar tools; they are SQL keywords.

Why it matters

Most analytical databases force a split: standard SQL for portable queries, a separate API or YAML file for everything platform-specific. AetheriusDB keeps it all in one grammar, so your schema reviews, code-review tools, and migration scripts work on a single source of truth.

• Drop-in for BI tools — Tableau, Metabase, Superset, and anything else that speaks the standard wire protocol can connect today.
• One grammar, many capabilities — time-travel, residency tiers, and quality predicates are first-class DDL, not side-files.
• Optional native compilation — heavy queries can be JIT-compiled to native code for extra speed. This is opt-in; see Query Data for how to enable it.

How you use it

Standard SQL needs no introduction. The recursive-CTE-plus-window example below is portable and runs unchanged from any PostgreSQL client.

-- Standard ANSI SQL: recursive CTE + window function.
WITH RECURSIVE org (mgr, emp, depth) AS (
  SELECT manager_id, employee_id, 1
  FROM employees WHERE manager_id IS NULL
  UNION ALL
  SELECT o.mgr, e.employee_id, o.depth + 1
  FROM employees e JOIN org o ON e.manager_id = o.emp
)
SELECT emp,
       RANK() OVER (PARTITION BY mgr ORDER BY depth)
FROM org;

-- Native extension: time-travel a table as it existed at a past moment.
SELECT * FROM sales
AS OF TIMESTAMP '2026-01-01 12:00:00'
WHERE region = 'EU';

The native extensions are additive: your portable SQL keeps working unchanged, and you adopt AS OF TIMESTAMP and the residency / quality clauses only where you want them.

Key concepts

Concept	What it means
ANSI surface	SELECT, JOIN, recursive CTEs, window functions, set operations.
AS OF TIMESTAMP	Read any table as it existed at a past moment — no backup restore needed.
Residency policy	A DDL clause that decides which storage tier a table’s rows prefer.
Quality CHECK	A constraint that validates rows at write time.

Tip

If you’re porting from PostgreSQL, start with the standard surface only, confirm your workload runs, then introduce native extensions one at a time. They’re additive — your portable SQL keeps working unchanged.

Heads up

Compatibility focuses on ANSI SQL and the most common PostgreSQL idioms. Vendor-specific extensions (custom procedural languages, exotic system catalogs, contrib extensions) are not portable verbatim. Run your suite against a test instance before committing to a migration.

SQL Grammar & Types →

The full type system, CTE rules, window semantics, and NULL handling.

Time Travel →

The history behind AS OF TIMESTAMP, branches, and rollback.

Query Data →

The query surface, JIT, and performance.