Limbo is a project to build the next evolution of SQLite.
Find a file
Pekka Enberg 793fa495e8 Merge 'Import JavaScript bindings test suite from libSQL' from Mikaël Francoeur
This PR imports the `sync` test suite from libSQL, and modifies the
export structure match `better-sqlite3`, so that at least a few tests
from the new test suite are passing.
I also changed the `package.json` to expose `wrapper.js` as an
entrypoint. I think the plain `index.js` was probably never meant to be
exposed directly to clients, because the wrapper does some important
transformation. It's also how libSQL-js is
[structured](https://github.com/tursodatabase/libsql-
js/blob/main/package.json#L20).
## DualTest test runner
The test suite that I imported was previously run twice, with different
environment variables: one run for libSQL-js, one run for better-
sqlite3. This worked well with libSQL, because it's compatible with
better-sqlite3. But Turso isn't there yet, so even though all tests need
to run on better-sqlite3, not all tests are passing on Turso.
To make it possible to run the test suite on both implementation, and to
make it possible to track the progress of Turso, I've added a `DualTest`
test runner that emulates the API of the Ava test runner, but instead of
a single `test()` function, it exposes two methods: `both()`, and
`onlySqlitePasses()`. The first one runs the test on both
implementations, and the second one also runs it on both, but expects
that Turso will fail.
When Turso is completely compatible with better-sqlite3, it will be easy
to remove the dual-test runner, since it has the same API as Ava.
## Future development
### Existing tests
The existing tests were divided in two files: `better-sqlite3.spec.mjs`,
and `dual-test.mjs` that are kept in sync manually. The first one is
mostly a superset of the second one, with additional tests indicating
behaviour that isn't implemented in Turso yet. I want to merge these
test suites to also use the dual-test test runner. This will make it
easier to evolve test suites and to track the progress of Turso.
### `SqliteError`
Modifying the test called `errors` to `both()` will show that Turso is
still missing an `SqliteError` type, to be compatible with better-
sqlite3. I have the required changes in a stash and will open a PR
shortly.
-----
as part of https://github.com/tursodatabase/turso/issues/1900

Closes #1941
2025-07-04 10:26:58 +03:00
.cargo add comment about config.toml env var 2025-02-15 15:05:36 +04:00
.github fix python test import naming 2025-07-03 02:15:08 -03:00
antithesis-tests antithesis: Fix Python linter complaints in parallel_driver_schema_rollback.py 2025-07-03 19:34:23 +03:00
assets Add Antithesis to README.md 2025-06-18 21:26:23 +03:00
bindings Merge 'Import JavaScript bindings test suite from libSQL' from Mikaël Francoeur 2025-07-04 10:26:58 +03:00
cli disable adaptive colors when output_mode is list 2025-07-03 23:31:51 +08:00
core Merge 'add libsql_disable_wal_checkpoint' from Pedro Muniz 2025-07-04 10:04:00 +03:00
docs Rename Limbo -> Turso in python tests 2025-07-02 10:57:46 -04:00
extensions Move series extension to core 2025-06-30 10:29:34 +03:00
fuzz Move UUID extension to core 2025-06-30 09:54:13 +03:00
licenses fix tests and return nan as null 2025-03-29 14:46:11 +02:00
macros Rename limbo_ext crate to turso_ext 2025-06-29 12:14:08 +03:00
perf add a benchmark for connection time versus number of tables 2025-07-01 20:10:21 -05:00
scripts antithesis: Make experiments run for longer 2025-07-03 15:58:49 +03:00
simulator leave io faults and fsync query disabled by default 2025-06-30 12:36:26 -03:00
simulator-docker-runner Fix URLs to point to github.com/tursodatabase/turso 2025-06-30 11:23:53 +03:00
sqlite3 move disable behavior to connection instead of checkpoint 2025-07-03 12:05:53 -03:00
stress Revert "Merge 'core: Disable ROLLBACK statement' from Pekka Enberg" 2025-07-03 12:36:48 +02:00
testing fix formatting create table in rollback.test 2025-07-03 12:36:48 +02:00
tests tests/integration: Fix write path test on Windows 2025-06-30 14:38:54 +03:00
vendored/sqlite3-parser Rename limbo_sqlite3_parser crate to turso_sqlite3_parser 2025-06-29 12:34:46 +03:00
.github.json Add Jussi to .github.json 2025-01-14 18:37:26 +02:00
.gitignore add simulator log to gitignore 2025-06-11 11:32:17 -03:00
.python-version setup uv for limbo 2025-04-15 12:45:46 -03:00
Cargo.lock Merge 'bindings/java: Rename to Turso' from Diego Reis 2025-07-04 10:06:19 +03:00
Cargo.toml Turso 0.1.1 2025-06-30 23:58:04 +03:00
CHANGELOG.md Update CHANGELOG.md 2025-06-30 23:57:52 +03:00
COMPAT.md Revert "Merge 'core: Disable ROLLBACK statement' from Pekka Enberg" 2025-07-03 12:36:48 +02:00
CONTRIBUTING.md rename Limbo to Turso in the README and other files 2025-06-27 15:44:40 -05:00
db.sqlite reset statement before executing 2025-05-02 19:26:44 -03:00
dist-workspace.toml cargo dist: s/limbo/turso/ 2025-07-04 10:13:50 +03:00
Dockerfile.antithesis core: Add Antithesis-aware turso_assert 2025-06-29 11:46:18 +03:00
flake.lock refator+feat: full flake overhaul 2025-01-30 18:24:19 -03:00
flake.nix add sqlite debug cli for nix. Fix cursor delete panic. Add tracing for cell indices in btree 2025-05-14 13:30:39 -03:00
LICENSE.md rename Limbo to Turso in the README and other files 2025-06-27 15:44:40 -05:00
Makefile cli: Remove extra binary 2025-06-19 09:41:01 +03:00
NOTICE.md rename Limbo to Turso in the README and other files 2025-06-27 15:44:40 -05:00
PERF.md rename Limbo to Turso in the README and other files 2025-06-27 15:44:40 -05:00
Pipfile Updated Pipfile 2024-07-12 13:07:34 -07:00
Pipfile.lock Added Pipfile and Pipfile.lock 2024-07-12 12:38:56 -07:00
pyproject.toml extract ruff lint rules to workspace 2025-06-20 15:59:03 -03:00
README.md clarify discord situation 2025-07-02 08:49:05 -05:00
rust-toolchain.toml Add clippy to rust-toolchain.toml... 2025-05-14 14:22:02 +03:00
turso.png Rename Limbo to Turso Database 2025-06-26 21:05:02 +03:00
uv.lock Rename Limbo -> Turso in python tests 2025-07-02 10:57:46 -04:00

Turso Database

Turso Database

Turso Database is an in-process SQL database, compatible with SQLite.

PyPI PyPI PyPI

Chat with the Core Developers on Discord

Chat with other users of Turso (and Turso Cloud) on Discord


Features and Roadmap

Turso Database is a work-in-progress, in-process OLTP database engine library written in Rust that has:

  • SQLite compatibility [doc] for SQL dialect, file formats, and the C API
  • Language bindings for JavaScript/WebAssembly, Rust, Go, Python, and Java
  • Asynchronous I/O support on Linux with io_uring
  • OS support for Linux, macOS, and Windows

In the future, we will be also working on:

  • BEGIN CONCURRENT for improved write throughput.
  • Indexing for vector search.
  • Improved schema management including better ALTER support and strict column types by default.

Getting Started

Please see the Turso Database Manual for more information.

💻 Command Line
You can install the latest `turso` release with:
curl --proto '=https' --tlsv1.2 -LsSf \
  https://github.com/tursodatabase/turso/releases/latest/download/turso_cli-installer.sh | sh

Then launch the shell to execute SQL statements:

Turso
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database
turso> CREATE TABLE users (id INT PRIMARY KEY, username TEXT);
turso> INSERT INTO users VALUES (1, 'alice');
turso> INSERT INTO users VALUES (2, 'bob');
turso> SELECT * FROM users;
1|alice
2|bob

You can also build and run the latest development version with:

cargo run
🦀 Rust
cargo add turso

Example usage:

let db = Builder::new_local("sqlite.db").build().await?;
let conn = db.connect()?;

let res = conn.query("SELECT * FROM users", ()).await?;
JavaScript
npm i @tursodatabase/turso

Example usage:

import { Database } from '@tursodatabase/turso';

const db = new Database('sqlite.db');
const stmt = db.prepare('SELECT * FROM users');
const users = stmt.all();
console.log(users);
🐍 Python
pip install pyturso

Example usage:

import turso

con = turso.connect("sqlite.db")
cur = con.cursor()
res = cur.execute("SELECT * FROM users")
print(res.fetchone())
🐹 Go
  1. Clone the repository
  2. Build the library and set your LD_LIBRARY_PATH to include turso's target directory
cargo build --package limbo-go
export LD_LIBRARY_PATH=/path/to/limbo/target/debug:$LD_LIBRARY_PATH
  1. Use the driver
go get github.com/tursodatabase/turso
go install github.com/tursodatabase/turso

Example usage:

import (
    "database/sql"
    _ "github.com/tursodatabase/turso"
)

conn, _ = sql.Open("sqlite3", "sqlite.db")
defer conn.Close()

stmt, _ := conn.Prepare("select * from users")
defer stmt.Close()

rows, _ = stmt.Query()
for rows.Next() {
    var id int
    var username string
    _ := rows.Scan(&id, &username)
    fmt.Printf("User: ID: %d, Username: %s\n", id, username)
}
Java

We integrated Turso Database into JDBC. For detailed instructions on how to use Turso Database with java, please refer to the README.md under bindings/java.

Contributing

We'd love to have you contribute to Turso Database! Please check out the contribution guide to get started.

FAQ

Is Turso Database ready for production use?

Turso Database is currently under heavy development and is not ready for production use.

How is Turso Database different from Turso's libSQL?

Turso Database is a project to build the next evolution of SQLite in Rust, with a strong open contribution focus and features like native async support, vector search, and more. The libSQL project is also an attempt to evolve SQLite in a similar direction, but through a fork rather than a rewrite.

Rewriting SQLite in Rust started as an unassuming experiment, and due to its incredible success, replaces libSQL as our intended direction. At this point, libSQL is production ready, Turso Database is not - although it is evolving rapidly. More details here.

Publications

  • Pekka Enberg, Sasu Tarkoma, Jon Crowcroft Ashwin Rao (2024). Serverless Runtime / Database Co-Design With Asynchronous I/O. In EdgeSys 24. [PDF]
  • Pekka Enberg, Sasu Tarkoma, and Ashwin Rao (2023). Towards Database and Serverless Runtime Co-Design. In CoNEXT-SW 23. [PDF] [Slides]

License

This project is licensed under the MIT license.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Turso Database by you, shall be licensed as MIT, without any additional terms or conditions.

Partners

Thanks to all the partners of Turso!

Contributors

Thanks to all the contributors to Turso Database!