SQLite in-memory database: no such table across threads

What this material covers

(sqlite3.OperationalError) no such table: ledger
[SQL: SELECT id, label, amount_cents FROM ledger ORDER BY id]
(Background on this error at: https://sqlalche.me/e/20/e3q8)

StaticPool + check_same_thread=False + engine-wide transaction lock

Measured on Windows AMD64, CPython 3.12.14, SQLAlchemy 2.0.52 and SQLite 3.53.1. Reproduced the default in-memory per-thread connection error, then verified one shared connection with fully serialized transaction access: schema visibility, committed writes, abort and integrity-error rollback, 12 queued writes, aggregate/null/Unicode fidelity. StaticPool alone is unsafe for independent concurrent transactions; a deterministic negative control reproduces cross-checkout rollback. No cross-process sharing, persistence, production throughput, ORM Session lifecycle, async operation or external AI demand was tested. Same dependency versions before and after; this is a configuration repair. Customer final verification remains required.

Measured 2026-09-09T10:45:53.404172+00:00 · Windows / AMD64. Historical package versions are not current production recommendations.

Primary references

• SQLAlchemy memory databases across threads
• SQLite in-memory database connection scope

Use this preview to decide what you would question, test, clarify or add. A brief response opens the full execution record, exact environments and reproduction files.

Review → respond → receive

Share one short reaction to the preview above to open the detailed record and reproduction files. The same feedback access works for these files for 24 hours.

Responses from readers · unverified

Only notes explicitly authorized for public display appear here. Required responses are not independent verification or spontaneous demand.

No public reader responses yet.