SQLiteEventBridge

​

Constructor params

• path: SQLite database file path
• table: table name (default abxbus_events)
• poll_interval: polling interval in seconds (default 0.25)
• name: optional bridge label

from abxbus import SQLiteEventBridge

bridge = SQLiteEventBridge(
    '/tmp/abxbus_events.sqlite3',
    table='abxbus_events',
    poll_interval=0.25,
    name='SqliteBridge',
)

import { SQLiteEventBridge } from 'abxbus'

const bridge = new SQLiteEventBridge('/tmp/abxbus_events.sqlite3', 'abxbus_events', 0.25, 'SqliteBridge')

​

Setup with a bus

from abxbus import EventBus, SQLiteEventBridge

bus = EventBus('AppBus')
bridge = SQLiteEventBridge('/tmp/abxbus_events.sqlite3')

bus.on('*', bridge.emit)
bridge.on('*', bus.emit)

import { EventBus, SQLiteEventBridge } from 'abxbus'

const bus = new EventBus('AppBus')
const bridge = new SQLiteEventBridge('/tmp/abxbus_events.sqlite3')

bus.on('*', bridge.emit)
bridge.on('*', bus.emit)

​

Behavior

• emit(...) upserts event payload fields into the configured table.
• on(...) auto-starts polling and registers handlers on the internal bus.
• Columns are created on demand only for event_* fields.
• The full event JSON is stored in event_payload (not just non-event_* fields).
• event_* columns are also stored as flat mirrored fields for indexing/querying.
• Writes use SQLite JSON functions for event_payload (for example json(?)).
• Rehydration merges event_payload with event_* column values back into a flat event object.
• Rows are read in (event_created_at, event_id) order, converted back to events, reset, and emitted locally.
• Runtime notes: Python uses stdlib sqlite3; TypeScript requires Node.js with built-in node:sqlite (Node 22+).