evoid-sqlite

SQLite storage engine for EVOID — Intent Handler system

Quick Start • Intent Handler • Config • API

Quick Start

uv add evoid-sqlite

Method 1: Intent Handler (Recommended)

from evoid_sqlite import register_handlers
from evoid.core.storage import storage_read, storage_write, storage_delete

# Register SQLite as storage handler
register_handlers(db_path="my_app.db")

# Use high-level API — goes through Intent pipeline
await storage_write("user:1", {"name": "Alice", "role": "admin"})
user = await storage_read("user:1")
await storage_delete("user:1")

Method 2: Direct API

from evoid_sqlite import create_storage

storage = create_storage("my_app.db")
await storage.write("user:1", {"name": "Alice"})
user = await storage.read("user:1")

Intent Handler

evoid-sqlite registers these Intent handlers:

How it works

1. register_handlers() registers Intent handlers for storage operations
2. storage_read() / storage_write() create Intents and execute through pipeline
3. Pipeline routes to SQLite handler
4. Handler connects to SQLite and performs operation

Configuration

TOML

[engines]
storage = "sqlite"

[engines.options.sqlite]
db_path = "data/my_app.db"

Python

from evoid.config import config

app = config(
    engines={
        "storage": "sqlite",
        "options": {
            "sqlite": {"db_path": "data/production.db"},
        },
    },
)

API

register_handlers(db_path: str)

Register SQLite as Intent handlers.

create_storage(db_path: str) -> SQLiteStorage

Factory function for direct API access.

Methods

Dependencies

• evoid>=0.4.3
• evoid-di>=0.1.0
• aiosqlite>=0.20.0

DI Integration

Registers as storage.sqlite in evoid-di:

from evoid_di import di

# Auto-registered when you call register_handlers()
di.register("storage.sqlite", lambda: SQLiteStorage("app.db"))

# Resolve with fallback
storage = di.resolve_with_fallback("storage.postgresql")
# Falls back to storage.sqlite if postgresql fails

Links

• EVOID Runtime
• Documentation
• Plugin Collection

License

MIT