arcature 2026.2.1

Arcature application framework: a high-level Application facade over the certified Arcature subsystems, with the low-level Axum/Tower escape hatch preserved.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26

//! The `db` subsystem facade (engine spec §18).
//!
//! Thin, namespaced re-export of the certified [`arcature_db`] crate. Gated by the
//! `db` Cargo feature so an application that does not use this subsystem pays
//! no compile cost. Items live under [`crate::db`] to avoid glob collisions
//! with other subsystems that re-export the same upstream crate.
//!
//! AP2.1-6 (ADR-0006): this facade also re-exports the high-level data layer
//! [`arcature_data`] (an internal `publish = false` workspace member) under
//! `crate::db::arcature_data`. The high-level surface is **additive**: the
//! existing `arcature_db::*` re-export is unchanged, and the new module is
//! reachable as `arcature::db::arcature_data::{Query, QueryModel, Page,
//! Transaction, ...}` plus the migration lint classifier. There is no new DB
//! engine, ORM, or hidden global pool — every `arcature_data` API takes the
//! `Db` handle explicitly.
//!
//! [`arcature_db`]: https://docs.rs/arcature_db

#![cfg(feature = "db")]

pub use arcature_db::*;

/// The high-level data layer over `arcature-db`: explicit-ownership query
/// ergonomics, typed transactions, N+1 detection (`n1` feature), and migration
/// lint. Re-exported additively under `arcature::db::arcature_data`.
pub use arcature_data;