cratestack-pg

The server-side facade for CrateStack: Postgres (via sqlx), Axum HTTP bindings, the generated Rust client runtime, and the shared schema / parser / policy / SQL surface.

When to use this crate

Pick cratestack-pg for backend services: HTTP servers, background workers, anything that needs the sqlx Postgres runtime, generated Axum routes, or the in-process generated Rust client.

For embedded / mobile / wasm targets (rusqlite, SQLite, wasm32), depend on cratestack-sqlite instead. The two crates are strictly disjoint by design — cratestack-pg does not pull in libsqlite3-sys, which lets you depend on the official sqlx umbrella crate alongside it without tripping Cargo's links = "sqlite3" collision rule.

Installation

Schema macros emit ::cratestack::* paths. Alias this crate as cratestack via Cargo's package = field:

[dependencies]
cratestack = { package = "cratestack-pg", version = "0.6.7" }

Then in code:

cratestack::include_server_schema!("schema/foo.cstack", db = Postgres);

SQL views

This facade re-exports ViewDelegate and ViewDelegateNoUnique — the read-only delegates handed out by runtime.views().<view_snake>() for every view block in the schema. ViewDelegate exposes find_many + find_unique and, on @@materialized views, a refresh() method that runs REFRESH MATERIALIZED VIEW CONCURRENTLY. ViewDelegateNoUnique (for @@no_unique views) exposes only find_many — find_unique and refresh() are absent at the type level. See the Views reference and ADR-0003.

Features

• postgres (default) — gates dep:cratestack-sqlx (and forwards cratestack-macros/postgres). On by default so every existing db = Postgres consumer sees zero behavior change. A consumer that only ever uses db = None schemas can disable it with default-features = false (re-adding whichever of decimal-rust-decimal/codec-json it still wants) to keep sqlx and its transitive dependency tree out of the build entirely — or depend on cratestack-api instead, which never pulls in cratestack-sqlx at all.
• decimal-rust-decimal (default) — Decimal columns use rust_decimal.
• decimal-bigdecimal — alternative bigdecimal backend.
• codec-json (default) — forwards the JSON codec to the generated client runtime, so include_client_schema! offers both CBOR and JSON.
• grpc — real transport grpc Rust codegen (server tonic service + Rust gRPC client). Off by default: pulls in tonic/prost for every consumer otherwise, whether or not they use gRPC. Without it, a Grpc schema fails include_server_schema!/include_client_schema! with a compile_error! pointing here.
• crypto-aws-lc-rs — not implemented yet, enabling it is a hard compile_error!. Reserved for a future FIPS-validated aws-lc-rs rustls provider; see install_fips_crypto_provider()'s doc comment and #334.