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
//! Real SQLite inside an Octra Circle.
//!
//! `octra-sqlite` provides a small Rust client for querying and writing to a
//! SQLite database whose engine runs inside an Octra `wasm_v1` Circle. The
//! crate keeps the first story deliberately small: create a [`Client`], open a
//! [`Database`], then run SQL.
//!
//! # Start here
//!
//! Public-read databases need no local wallet or config:
//!
//! ```no_run
//! use octra_sqlite::{Client, Result};
//!
//! fn main() -> Result<()> {
//! let client = Client::default();
//! let db = client.database(
//! "oct://devnet/octQfYK2fE9RvR9kfj8FJfMBQw1e4EzfHB8Q5Z9J2DCnRBQ",
//! )?;
//! let rows = db.query("select id, name from artist order by id;")?;
//! println!("{} rows", rows.row_count);
//! Ok(())
//! }
//! ```
//!
//! # Configured databases and writes
//!
//! [`Client::from_default_config`] loads the same saved database and wallet
//! configuration used by the CLI. Writes are owner-signed and confirmed by
//! default:
//!
//! ```no_run
//! use octra_sqlite::{Client, Result};
//!
//! fn main() -> Result<()> {
//! let client = Client::from_default_config()?;
//! let db = client.database("art")?;
//! let result = db.execute("insert into artist(name) values ('Hokusai');")?;
//! println!("confirmed: {}", result.submitted.tx_hash.is_some());
//! Ok(())
//! }
//! ```
//!
//! Use [`Database::execute_no_wait`] when submission and confirmation must be
//! separate, then complete the lifecycle with [`Database::wait`].
//!
//! # Read and write model
//!
//! Sealed databases use signed Octra view auth for reads. Public-read
//! databases use unsigned Octra Circle views for SQL reads while keeping writes
//! owner-signed through OSW1 owner write intent. Pass a saved database name or a
//! full `oct://NETWORK/<circle>` URI to [`Client::database`]. The client
//! detects the Circle's Octra read surface unless `read_mode` is explicitly set.
//! Sealed authenticates reads; it does not encrypt data or make reads owner-only.
//! Write SQL and values are visible in Octra transaction history.
//!
//! # API map
//!
//! - [`Client`] owns configuration and transport; [`Database`] owns one opened
//! SQL data plane.
//! - [`QueryResult`], [`ExecuteResult`], and [`SubmittedTransaction`] model the
//! query, confirmed-write, and submitted-write lifecycles.
//! - [`AuthInfo`], [`ProgramInfo`], and [`ReadMode`] expose database and Circle
//! state without leaking raw RPC details into the first story.
//! - [`client`] contains advanced transport, config, and signing types.
//! - [`client::raw`] contains lower-level Octra RPC plumbing for adapters and
//! operational tooling.
//! - [`protocol`] contains the transport-independent OSR1, OSW1, target, and
//! transaction wire formats.
//!
//! # Errors
//!
//! [`Error::kind`] is the stable broad category for application handling.
//! [`Error::code`] preserves a more precise machine-readable code supplied by
//! the RPC, Circle, or receipt, or assigned at a local protocol boundary.
//! Human error text is not an automation contract.
//!
//! # Build configuration
//!
//! - `cli`: build the `octra-sqlite` command line interface.
//! - `http`: include the default blocking HTTP RPC transport.
//! - `wasm-behavior`: enable host-harness tests for the bundled Circle WASM.
//!
//! docs.rs builds the library with `http` and without the CLI. The default
//! crate configuration includes both `cli` and `http`.
//!
//! # Stability
//!
//! The CLI JSON envelopes and OSR1/OSW1 wire formats are treated as public
//! surfaces. The Rust API is still `0.x`; breaking Rust API cleanup happens in
//! minor versions.
pub use ;
pub use ReadMode;
pub use Value;
/// Human and automation CLI entrypoints.