dirsql (Python SDK)
Ephemeral SQL index over a local directory. dirsql watches a filesystem, ingests structured files into an in-memory SQLite database, and exposes a SQL query interface -- the filesystem is always the source of truth.
Also available as dirsql on crates.io and dirsql on npm.
Installation
pip install dirsql
Requires Python >= 3.12. Ships as a native extension (Rust via PyO3); prebuilt binary wheels are provided for common platforms.
Quick start
DirSQL is async by default: the constructor returns immediately, scanning runs in a background thread, and you await db.ready() before querying. Each table is a (ddl, glob, extract) triple: the DDL defines the SQLite schema, the glob selects files (relative to the root), and extract turns a matched file into a list of row dicts. dirsql does not read file contents -- if extract needs the file body it reads path itself; return an empty list to skip a file.
import asyncio
import json
from dirsql import DirSQL, Table
async def main():
db = DirSQL(
"./my-blog",
tables=[
Table(
ddl="CREATE TABLE posts (title TEXT, author TEXT)",
glob="posts/*.json",
extract=lambda path: [json.loads(open(path, encoding="utf-8").read())],
),
],
)
await db.ready()
posts = await db.query("SELECT * FROM posts WHERE author = 'alice'")
print(posts)
asyncio.run(main())
Multiple tables and joins
db = DirSQL(
"./my-blog",
tables=[
Table(
ddl="CREATE TABLE posts (title TEXT, author_id TEXT)",
glob="posts/*.json",
extract=lambda path: [json.loads(open(path, encoding="utf-8").read())],
),
Table(
ddl="CREATE TABLE authors (id TEXT, name TEXT)",
glob="authors/*.json",
extract=lambda path: [json.loads(open(path, encoding="utf-8").read())],
),
],
)
await db.ready()
results = await db.query("""
SELECT posts.title, authors.name
FROM posts JOIN authors ON posts.author_id = authors.id
""")
Ignoring files
Pass ignore patterns to skip files during scanning and watching:
db = DirSQL(
"./my-blog",
ignore=["**/drafts/**", "**/.git/**"],
tables=[...],
)
Path-table scans (SELECT ... FROM './') respect .gitignore files by
default. Pass no_ignore=True to restore the full walk; the built-in
node_modules/.git defaults and any ignore patterns still apply:
db = DirSQL("./my-blog", no_ignore=True)
Loading SQLite extensions
Pass extensions to load SQLite extension shared libraries onto the connection at startup (before any CREATE TABLE). Each entry is a dict with a path and an optional entrypoint init-symbol override:
db = DirSQL(
"./my-blog",
tables=[...],
extensions=[
{"path": "./ext/vec0.dylib", "entrypoint": "sqlite3_vec_init"},
{"path": "./ext/myext.so"}, # entrypoint derived from the filename
],
)
await db.ready()
# The extension's functions are now callable in queries:
rows = await db.query("SELECT vec_version() AS v")
dirsql enables extension loading only while loading the configured libraries, then disables it again, so the SQL load_extension() function is never exposed to your queries. Programmatic entries load first, followed by any [[dirsql.extension]] entries declared in a config file. See the config reference.
Watching for changes
db.watch() returns an async iterator of row-level change events as files change on disk:
async for event in db.watch():
print(f"{event.action} on {event.table}: {event.row}")
if event.action == "error":
print(f" error: {event.error}")
Each event has .action ("insert", "update", "delete", or "error"), .table, .row (the new row, or the deleted row on delete), .old_row (the previous row, on update), .file_path, and .error (on error).
CLI
pip install dirsql also installs a dirsql console script. dirsql "<sql>" (or uvx dirsql "<sql>") runs one query and prints the rows as JSON — the default. dirsql server starts an HTTP server exposing the SDK over HTTP: POST /query for SQL and GET /events for a Server-Sent Events change stream. See the CLI reference.
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for dirsql 0.4.85
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dirsql-0.4.85.tar.gz | 592.6 kB | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| dirsql-0.4.85-cp310-abi3-win_amd64.whl | CPython 3.10 | abi3 | Windows x86-64 | Details |
| dirsql-0.4.85-cp310-abi3-manylinux_2_28_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.28+ x86-64 | Details |
| dirsql-0.4.85-cp310-abi3-manylinux_2_28_aarch64.whl | CPython 3.10 | abi3 | Linux glibc 2.28+ ARM64 | Details |
| dirsql-0.4.85-cp310-abi3-macosx_11_0_arm64.whl | CPython 3.10 | abi3 | macOS 11.0+ ARM64 | Details |
| dirsql-0.4.85-cp310-abi3-macosx_10_12_x86_64.whl | CPython 3.10 | abi3 | macOS 10.12+ x86-64 | Details |
Total release size: 17.5 MB
Release files / dirsql-0.4.85.tar.gz
| Download URL | dirsql-0.4.85.tar.gz |
|---|---|
| Size | 592.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2525f9a13c45f5b77240e44540f603d85dd5ec9dcd27fbf1d476a3f2d82782cb
|
|
BLAKE2b-256 checksum How to use checksums |
2bea9b34e458c99375001831c033b6b6d0aec1567bfec1bde3ec55ff68519693
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logRelease files / dirsql-0.4.85-cp310-abi3-win_amd64.whl
| Download URL | dirsql-0.4.85-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 3.5 MB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
4f921a46304bb37f7f3ceee3c86fa963d026776f91fc131a709b5f62de42b815
|
|
BLAKE2b-256 checksum How to use checksums |
5e2b896f1616fe3f9f1f9ebf2b4ffab238363f3a217452c3c6405123c6829f20
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logRelease files / dirsql-0.4.85-cp310-abi3-manylinux_2_28_x86_64.whl
| Download URL | dirsql-0.4.85-cp310-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 3.6 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
01887c6129aa5c25484cdc75981f1c71349a42a51579a8a47ff4d99976f5a52d
|
|
BLAKE2b-256 checksum How to use checksums |
f0f274ae13c5ee01e4d9575b8e3bb0faf242a883ed68cf73ee703b74f6881a61
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logRelease files / dirsql-0.4.85-cp310-abi3-manylinux_2_28_aarch64.whl
| Download URL | dirsql-0.4.85-cp310-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 3.4 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
14ba4ccab6218ef36637c46afb6d53cc6d06fea506ad41a2742db8733a5d48ef
|
|
BLAKE2b-256 checksum How to use checksums |
1fa26f9c05aa6a61c11405879bed347831c43dcec400d504837ffb6b71065081
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logRelease files / dirsql-0.4.85-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | dirsql-0.4.85-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 3.1 MB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
b6ebae8853fa969952c2d025ab509ba6b2892f0c1d7ce0c3fd6042ad126d6fd8
|
|
BLAKE2b-256 checksum How to use checksums |
fd8795c40034d9e4eeb2f4319d372ca8522855307509d3178b0ee7fd0649b372
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logRelease files / dirsql-0.4.85-cp310-abi3-macosx_10_12_x86_64.whl
| Download URL | dirsql-0.4.85-cp310-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 3.3 MB |
| Tags | CPython 3.10 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
494854312896855fccc0a20133af67f5e8dacdcf7140b9dfe7e395552602e559
|
|
BLAKE2b-256 checksum How to use checksums |
2134bb373b3e7af2d16520cf97a4f047fe134eac638b348a34d48bdf7dcb1f13
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency log
