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
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
// SPDX-License-Identifier: AGPL-3.0-or-later
// SochDB - LLM-Optimized Embedded Database
// Copyright (C) 2026 Sushanth Reddy Vanagala (https://github.com/sushanthpy)
//
// This program is free software: you can redistribute it and/or modify
// it under the terms of the GNU Affero General Public License as published by
// the Free Software Foundation, either version 3 of the License, or
// (at your option) any later version.
//
// This program is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
// GNU Affero General Public License for more details.
//
// You should have received a copy of the GNU Affero General Public License
// along with this program. If not, see <https://www.gnu.org/licenses/>.
//! Unified Transaction Coordinator
//!
//! This module defines the canonical transaction management interface for SochDB.
//! It consolidates the functionality of multiple transaction managers:
//!
//! ## Implementation Guide
//!
//! **The live concurrency contract is multi-reader, single-writer.** Production
//! isolation and durability run through `DurableStorage` (`database.rs` /
//! `durable_storage.rs`): lock-free MVCC snapshot reads via `ConcurrentMvcc`,
//! writes serialized by a single-writer lock (`acquire_writer`, "serialize WAL
//! commits across processes"), and SSI conflict validation via `MvccManager`.
//! WAL crash recovery is wired here (`txn_wal` / `RecoveryStats` /
//! `durability_contract`). There is **no concurrent-writer (wired SSI) path on
//! the live engine** — do not assume one exists.
//!
//! SochDB contains three transaction-manager types; only the first is on the
//! live path:
//!
//! ### 1. `DurableStorage` + `MvccManager` (durable_storage.rs) — LIVE / PRODUCTION
//!
//! The actual production path. Single-writer write coordination + MVCC snapshot
//! reads, with `MvccManager` providing SSI rw-antidependency validation and the
//! storage layer providing WAL durability and crash recovery.
//!
//! ### 2. `MvccTransactionManager` (wal_integration.rs) — STANDALONE, NOT WIRED
//!
//! A complete, self-contained manager (WAL durability, MVCC snapshot isolation,
//! optional SSI, group commit, version-chain GC). Despite being feature-rich it
//! has **no functional caller in the engine** — `DurableStorage` does not use
//! it — so it is **not** the production path. Use it only if you explicitly
//! construct and own one; it does not participate in the live database's
//! single-writer concurrency contract. (Its SSI read/write tracking is correct
//! as of the Task 1B id-divergence fix, but it remains unwired.)
//!
//! ```ignore
//! use sochdb_storage::wal_integration::MvccTransactionManager;
//! let txm = MvccTransactionManager::new("wal.log", |_key, _value| Ok(()))?;
//! let txn_id = txm.begin(IsolationLevel::Serializable)?;
//! txm.write(txn_id, b"key", b"value")?;
//! txm.commit(txn_id)?;
//! ```
//!
//! ### 3. `TransactionManager` (mvcc_snapshot.rs) — `#[deprecated]`
//!
//! Minimal snapshot isolation without durability. Unit tests / ephemeral
//! in-memory only. **Not for production workloads requiring crash recovery.**
//!
//! ## Transaction Coordinator Trait
//!
//! The `TransactionCoordinator` trait unifies the common interface:
use Result;
// Re-export TransactionMode from durable_storage (canonical definition)
pub use crateTransactionMode;
/// Isolation level for transactions
/// Transaction handle returned by begin operations
/// Unified transaction coordinator interface
///
/// This trait defines the canonical API for transaction management.
/// All new transaction manager implementations should implement this trait.
///
/// ## Durability Contract
///
/// Implementations MUST document their durability guarantees:
/// - `Durable`: Committed transactions survive crash (WAL + fsync)
/// - `Ephemeral`: No durability guarantee (in-memory only)
/// Durability guarantee level
/// Recovery statistics returned after crash recovery
// =============================================================================
// Re-exports for convenience
// =============================================================================
// Note: The canonical implementation is MvccTransactionManager from wal_integration
// pub use crate::wal_integration::MvccTransactionManager;