Expand description
Single entry point for the toolu-orm workspace.
toolu-orm is a facade: it contains no logic of its own, only re-exports
of the four library crates, all pinned to one version.
toolu-orm = { version = "0.1", features = ["postgres"] }| Re-export | Crate | Holds |
|---|---|---|
core | toolu-orm-core | schema, columns, migrations, driver traits |
query | toolu-orm-query | select / insert / update / delete builders |
connection | toolu-orm-connection | pools and driver adapters |
table, ColumnEnum, FromRow, Relational | toolu-orm-macros | proc macros |
§Features
libsql, rusqlite and postgres forward to every re-exported crate, so
one feature list drives the whole stack. Enable exactly one: toolu-orm-query
compiles its executor and transaction code only for a single driver.
§Macro paths
The proc macros expand to absolute paths resolved against the consuming
crate’s Cargo.toml: ::toolu_orm::core::… when this facade is the
dependency, ::toolu_orm_core::… when the crates are named directly. So
toolu-orm on its own is enough — import the macro and nothing else:
use toolu_orm::table;
#[table(name = "users")]
pub struct User {
pub id: i64,
pub email: String,
}The prelude remains for code that names toolu_orm_core,
toolu_orm_query or the driver crate itself; the macros do not need it.
Re-exports§
pub use toolu_orm_connection as connection;pub use toolu_orm_core as core;pub use toolu_orm_query as query;
Modules§
- prelude
- The macros plus the crate names they used to require.
Attribute Macros§
- fts5_
table - Declares a
CREATE VIRTUAL TABLE … USING fts5(…)table. - table