BUG: Implement Thread-Safe Database Connection Management

[sujal111]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

The current implementation in
connection.py
uses check_same_thread=False which disables SQLite's thread safety checks, potentially leading to race condition plus inconsistent application state

this code snippet is causing it :)
conn = sqlite3.connect(DATABASE_PATH, check_same_thread=False,)

@rahulharpal1603 - let me know if I can work on this issue

Record

• I agree to follow this project's Code of Conduct

[github-actions]

👋 Thanks for opening this issue! The maintainers will review it shortly. Till then, do not open any PR. This is a strict rule we like to follow around here :)

[prabalpatkar558412-collab]

Hi @rahulharpal1603 👋

I’ve reviewed the current connection.py implementation and understand the concern around using
sqlite3.connect(..., check_same_thread=False).

Disabling SQLite’s thread check allows multiple threads to share a single connection, which can lead to race conditions, inconsistent transactions, and subtle data corruption under concurrent access. This is especially risky because SQLite connections are not designed to be safely shared across threads without external synchronization.

For a fix, I’m planning to:

• Remove the global shared connection
• Introduce thread-safe connection management using either:
  • per-thread connections via threading.local(), or
  • a context-managed connection lifecycle to ensure isolation and proper cleanup
• Ensure that each thread/request gets its own SQLite connection without relying on check_same_thread=False
• Add safeguards to prevent accidental cross-thread connection reuse

I’d be happy to take this up and implement a clean, maintainable solution aligned with SQLite’s concurrency model.
Please let me know if I can proceed with this issue.

Thanks!

[rohan-pandeyy]

Hi @prabalpatkar558412-collab, using threading.local() could potentially introduce a risk of SQLite file lock. When implementing the thread-safe connection factory, we should explicitly enable WAL. Refer to this documentation: https://sqlite.org/wal.html#activating_and_configuring_wal_mode