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
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
//! Shared SQL [`SchedulerStore`](chronon_core::store::SchedulerStore) for `PostgreSQL` and `SQLite`.
//!
//! Backend and platform engineers use this crate when implementing or extending SQL persistence.
//! Application binaries should prefer the thin wrappers
//! [`chronon_backend_postgres`](https://docs.rs/chronon-backend-postgres) or
//! [`chronon_backend_sqlite`](https://docs.rs/chronon-backend-sqlite).
//!
//! ## Stack position
//!
//! ```text
//! chronon-backend-{postgres,sqlite} → chronon-backend-sql-common → chronon-core
//! ```
//!
//! ## Entry points
//!
//! - [`SqlSchedulerStore`] — connect, schema bootstrap, and trait implementation
//! - [`SqlDialect`] / [`SqlPool`] — engine selection and pool wrapper
//! - [`bind_sql`] — dialect-specific placeholder rewriting (`?` → `$1`, …)
//! - [`validate_postgres_schema_name`] — allowlist for isolated schema DDL / `search_path`
//!
//! ## Prerequisites
//!
//! Schema bootstrap runs on connect. For parallel Postgres tests use
//! [`SqlSchedulerStore::connect_postgres_isolated`] (schema names must match
//! [`validate_postgres_schema_name`]).
//!
//! ## Example
//!
//! ```rust,no_run
//! use chronon_backend_sql_common::SqlSchedulerStore;
//!
//! # async fn example() -> chronon_core::Result<()> {
//! let store = SqlSchedulerStore::connect_sqlite("sqlite://:memory:").await?;
//! # Ok(())
//! # }
//! ```
pub use ;
pub use LEADER_ROW_ID;
pub use run_pool_key;
pub use ;