Skip to main content

Crate dactyl_db

Crate dactyl_db 

Source
Expand description

Dactyl — the backend-neutral datastore boundary for Decapod.

The public API contains no rusqlite or HTTP adapter types. Callers can use one-shot functions for small operations or retain a Connection for migrations, validation probes, and several operations against one route. Both paths use the same parameter, row, transaction, and SQL-analysis contracts.

Re-exports§

pub use crate::error::DactylError;
pub use crate::query::Construct;
pub use crate::query::Dialect;
pub use crate::query::QueryAnalyzer;

Modules§

error
Public error type for dactyl.
query
Query analysis and bounded dialect preparation.

Macros§

query
dactyl::query!("literal") — returns the rewritten SQL as a String.

Structs§

Connection
A connection-scoped backend-neutral datastore handle.
ConnectionOptions
Per-connection behavior that is safe to expose across all adapters.
DatastoreRoute
Explicit route information for a backend connection.
Row
One result row. Carries the column names plus the per-cell JSON values.
Rows
A collection of result rows.
Statement
A parameterized SQL statement for batch execution.

Enums§

Datastore
A backend selected by a DatastoreRoute.
Parameter
A unified database parameter value.
SqliteJournalMode
SQLite journal policy. Wal is the default for concurrent local readers; the adapter falls back to Delete if the filesystem cannot support WAL.
StorageOp
Operation-based storage contract for integration boundaries.
StorageResult
Results for StorageOp.

Functions§

execute
Execute one DDL/migration/affected-row statement.
execute_batch
Execute a caller-owned SQL script.
query
Execute any query against the active environment-selected datastore.
transaction
Execute an atomic batch of parameterized statements.