Skip to content

Current Status and Limits

xuji755 edited this page Oct 9, 2026 · 1 revision

Current status and limits

This page describes the v0.2.0 development line. It separates working interfaces from design targets.

Available now

  • Durable page storage, buffer pool, heap tables, B+Tree, WAL/Undo, recovery, transactions and checkpoints.
  • Relational DDL/DML, aggregates, two-table joins, set operations, INSERT … SELECT, named parameters and rule-based index access.
  • Local CLI, SQL*Plus-style client, Rust/Python drivers, password authentication and owner-bound private workspaces.
  • Read-only dictionary queries and structure-only workspace templates.
  • Native transactional property graphs with forward and reverse adjacency.
  • A bounded Cypher subset, graph writes, PROFILE CYPHER, property indexes and SQL GRAPH_TABLE.
  • Native BM25 graph full-text search for nodes and relationships, fixed JSON paths and deferred maintenance.

Important limits

  • Statements are serialized by one instance executor even when several clients are connected.
  • Cypher 25 is not complete. APOC, GDS, arbitrary user procedures/functions and unbounded traversal are unavailable.
  • Graph vector and spatial indexes are unavailable.
  • Full text has its own query and scoring contract; it is not Lucene-compatible.
  • Rebuilding property or full-text indexes does not yet reclaim retired physical segments.
  • The old full-text format is upgraded by a complete first maintenance pass.
  • Remote TCP transport, hot backup/PITR and log rotation are unfinished.
  • Production-size graph benchmarks for latency, throughput, memory, disk and recovery time have not been completed.

Deployment decision

Use the current build for development, integration testing and controlled trials. Validate representative graph size, query depth, full-text update rate, recovery time and disk growth before production use. Do not treat compatibility with Neo4j or PostgreSQL AGE as an implemented contract.

Clone this wiki locally