mirror of
https://github.com/trailbaseio/trailbase.git
synced 2026-02-12 04:29:26 -06:00
6cbea390fb
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.
16 lines
597 B
Plaintext
16 lines
597 B
Plaintext
[submodule "vendor/refinery"]
|
|
path = vendor/refinery
|
|
url = git@github.com:trailbaseio/refinery.git
|
|
[submodule "vendor/sqlite_loadable"]
|
|
path = vendor/sqlite-loadable
|
|
url = git@github.com:trailbaseio/sqlite-loadable-rs.git
|
|
[submodule "vendor/sqlean/bundled/sqlean"]
|
|
path = vendor/sqlean/bundled/sqlean
|
|
url = https://github.com/trailbaseio/sqlean
|
|
[submodule "vendor/tokio-rusqlite"]
|
|
path = vendor/tokio-rusqlite
|
|
url = https://github.com/trailbaseio/tokio-rusqlite.git
|
|
[submodule "vendor/serde_rusqlite"]
|
|
path = vendor/serde_rusqlite
|
|
url = https://github.com/trailbaseio/serde_rusqlite.git
|