Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

qail.rs Parity Status

qail-zig tracks qail.rs as the reference implementation for PostgreSQL driver behavior and hardening.

Current Snapshot

As of 2026-03-28, the narrow AST/codegen parity checks against /Users/orion/qail.rs are green:

  • ./scripts/check_codegen_sync.sh /Users/orion/qail.rs -> codegen sync check passed
  • ./scripts/check_parity.sh /Users/orion/qail.rs -> AST actions: rust=75 zig=76, Encoder actions: rust=57 zig=76, parity check passed

That means the Rust-driven AST porting/codegen path is working for its current scope, and the PostgreSQL AST encoder still covers the Rust action surface completely.

Active Areas with Strong Coverage

  • AST core exports
  • Rust-driven AST codegen sync
  • PostgreSQL wire protocol
  • prepared execution and pipelines
  • pooling
  • TLS transport
  • COPY in/out helpers
  • LISTEN / NOTIFY
  • logical replication core
  • RLS helper APIs
  • startup/auth policy controls
  • protocol hardening suites

Current Reality

Parity is not complete across the entire qail.rs ecosystem. The largest gaps remain outside the core PG driver track:

  • gateway / auto-REST / WebSocket / OpenAPI stack
  • qdrant vector driver and hybrid execution path
  • workflow engine
  • typed schema codegen (qail types) and build-time SQL / N+1 guard rails
  • some CLI breadth (qail init, exec, types, vector/hybrid flows)
  • some LSP breadth (notably formatting and code actions)
  • direct SDKs and broader non-driver surfaces

Important Policy Delta

There is still one meaningful runtime policy difference between the repos:

  • qail.rs removed raw runtime SQL APIs from the normal execution path.
  • qail-zig still carries .raw in the AST for trusted/local use.
  • Current mitigation: validateAst rejects .raw and other procedural escape hatches for untrusted or deserialized AST ingress.

PG Driver Focus

The PG driver is the serious parity target right now. That is why recent work landed in:

  • sanitization
  • startup/auth sequencing
  • protocol hardening
  • replication hardening
  • benchmark comparability

For detailed driver parity notes, see the repository parity file:

  • PARITY_AST_PG_DRIVER.md