trailbase/trailbase-sqlite/Cargo.toml

[package]
name = "trailbase-sqlite"
version = "0.2.0"
edition = "2021"
license = "OSL-3.0"
description = "Async SQLite connection for TrailBase"
homepage = "https://trailbase.io"
repository = "https://github.com/trailbaseio/trailbase"
readme = "../README.md"
autobenches = false

[[bench]]
name = "benchmark"
path = "benches/benchmark.rs"
harness = false

[dependencies]
crossbeam-channel = "0.5.13"
log = { version = "^0.4.21", default-features = false }
parking_lot = { version = "0.12.3", default-features = false }
rusqlite = { workspace = true }
serde = { version = "^1.0.203", features = ["derive"] }
serde_json = "1.0.122"
serde_rusqlite = "0.38.0"
thiserror = "2.0.1"
tokio = { workspace = true }

[dev-dependencies]
criterion = { version = "0.5", features = ["html_reports", "async_tokio"] }
env_logger = { workspace = true }
futures-util = { version = "0.3", default-features = false, features = ["alloc"] }
log = "0.4.27"
rand = "0.9.0"
tempfile = "3.19.1"
trailbase-extension = { workspace = true }
uuid = { workspace = true }
Squash all commits for a fresh start. This is only to avoid accidentally leaking any secrets from early development especially in the light of short-sha attacks. 2024-10-30 22:38:29 +00:00			`[package]`
			`name = "trailbase-sqlite"`
Publish updated crates: trailbase(\|-sqlite\|-extension). 2025-03-09 11:08:46 +00:00			`version = "0.2.0"`
Squash all commits for a fresh start. This is only to avoid accidentally leaking any secrets from early development especially in the light of short-sha attacks. 2024-10-30 22:38:29 +00:00			`edition = "2021"`
Re-re-license from AGPLv3 to the weaker copyleft OSL-3.0. After spending too much time researching licenses, my laymen understanding makes me feel that OSL-3.0 will be a better match given TrailBase's rare dual use as a standalone backend or framework. It tried to outline the reasoning in the README.md. I would appreciate input from anyone more experienced with licenses. For now, I would like to turn my attention back to more technical issues :hide:. 2024-11-02 11:10:01 +00:00			`license = "OSL-3.0"`
Restructure crates: make the sqlite execution model more standalone, i.e. move more extension stuff back to extension crate and schema stuff to a new schema crate. 2025-04-08 10:25:10 +00:00			`description = "Async SQLite connection for TrailBase"`
Prepare trailbase-sqlite for publishing. 2024-12-30 10:52:02 +00:00			`homepage = "https://trailbase.io"`
			`repository = "https://github.com/trailbaseio/trailbase"`
			`readme = "../README.md"`
Add read benchmarks to trailbase-sqlite. 2025-04-12 11:09:22 +00:00			`autobenches = false`
Squash all commits for a fresh start. This is only to avoid accidentally leaking any secrets from early development especially in the light of short-sha attacks. 2024-10-30 22:38:29 +00:00
Add a benchmark scaffold to sqlite. 2025-04-11 19:57:51 +00:00			`[[bench]]`
			`name = "benchmark"`
Add read benchmarks to trailbase-sqlite. 2025-04-12 11:09:22 +00:00			`path = "benches/benchmark.rs"`
Add a benchmark scaffold to sqlite. 2025-04-11 19:57:51 +00:00			`harness = false`

Squash all commits for a fresh start. This is only to avoid accidentally leaking any secrets from early development especially in the light of short-sha attacks. 2024-10-30 22:38:29 +00:00			`[dependencies]`
Move SQLite orchestration into trailbase-sqlite and fix js-runtime completion bug with true async (previously libsql was sync under the hood). 2024-12-04 15:57:15 +00:00			`crossbeam-channel = "0.5.13"`
Extend `trailbase-sqlite`s execution model to allow for parallel reads. This reduces the latency long-tail for slow reads. Note that this complicates the APIs, since it pushes the responsibility of declaring a query a read or write to the user to then be scheduled appropriately. Add `.(read_\|)query_row_f` APIs similar to rusqlites `conn.query_row` accepting a `\|row\| -> Result<T>` to reduce the use of `Row` and `Rows`. Make benchmarks more isolated by not sharing a DB across runs accumulating writes. 2025-04-08 14:56:19 +00:00			`log = { version = "^0.4.21", default-features = false }`
Fix logging: deterministically and separately initialize `log` and `tracing`. 2025-04-04 11:23:26 +00:00			`parking_lot = { version = "0.12.3", default-features = false }`
Herculean migration from libsql's rust bindings to plain rusqlite+SQLite. There's a couple of reasons: * As for the rust bindings: they're sub-par to rusqlite, though rusqlite is amazing. Even libsql-server uses rusqlite over their own bindings. The bindings are missing features such as update hooks and the hard-coded execution model suffers from lock congestion. * We've fixed bugs (e.g. trivial null ptr accesses went unnoticed), raised issues, and tried to add missing functionality such as update hooks. It's unclear if the rust-bindings are a priority or covered by the principles laid out in the libsql manifesto. From the outside it looks like focus has shifted to https://github.com/penberg/limbo. * As for the C-libsql fork for SQLite itself, it's getting more and more outdated (2024-01-30 (3.45.1)) and it's unclear when and if the ideas from the manifesto will manifest. Looking forward this opens the door for TrailBase to: * Bundle more recent versions of SQLite * Implement more performant, better scaling execution models. * Implement realtime APIs for subscribing to data changes. 2024-11-29 12:35:55 +00:00			`rusqlite = { workspace = true }`
Squash all commits for a fresh start. This is only to avoid accidentally leaking any secrets from early development especially in the light of short-sha attacks. 2024-10-30 22:38:29 +00:00			`serde = { version = "^1.0.203", features = ["derive"] }`
			`serde_json = "1.0.122"`
Update rusqlite: v0.33 -> v0.34. 2025-03-10 13:10:18 +00:00			`serde_rusqlite = "0.38.0"`
Update rust dependencies. 2024-11-08 20:46:30 +00:00			`thiserror = "2.0.1"`
Minor: consistent tokio and env_logger dependencies. 2025-04-14 07:25:44 +00:00			`tokio = { workspace = true }`
Restructure crates: make the sqlite execution model more standalone, i.e. move more extension stuff back to extension crate and schema stuff to a new schema crate. 2025-04-08 10:25:10 +00:00
			`[dev-dependencies]`
Add a benchmark scaffold to sqlite. 2025-04-11 19:57:51 +00:00			`criterion = { version = "0.5", features = ["html_reports", "async_tokio"] }`
Minor: consistent tokio and env_logger dependencies. 2025-04-14 07:25:44 +00:00			`env_logger = { workspace = true }`
Add a mixed query benchmark to trailbase-sqlite and make all benchmarks concurrently hammer the connection. 2025-04-12 13:23:17 +00:00			`futures-util = { version = "0.3", default-features = false, features = ["alloc"] }`
Add a benchmark scaffold to sqlite. 2025-04-11 19:57:51 +00:00			`log = "0.4.27"`
Make query mix benchmark's slow queries slower and group benchmarks with throughput as requested. 2025-04-13 09:09:48 +00:00			`rand = "0.9.0"`
Add a benchmark scaffold to sqlite. 2025-04-11 19:57:51 +00:00			`tempfile = "3.19.1"`
Prepare trailbase-sqlite for publishing. 2024-12-30 10:52:02 +00:00			`trailbase-extension = { workspace = true }`
Update Rust and JS deps. 2025-02-26 23:27:37 +00:00			`uuid = { workspace = true }`