How does Jinbase handle concurrency? Since it’s built on SQLite, does it inherit SQLite’s locking mechanisms, or have you implemented additional features to manage concurrent access across the different data models?
To interact with SQLite, Jinbase uses LiteDBC [1] an SQL interface compliant with the DB-API 2.0 specification described by PEP 249 [2], itself wrapping Python's sqlite3 [3] module for a more intuitive interface and multithreading support by default. I wrote for LiteDBC a stress test [4] involving concurrency with Asyncpal [5].
[1] https://github.com/pyrustic/litedbc
[2] https://peps.python.org/pep-0249/
[3] https://docs.python.org/3/library/sqlite3.html
[4] https://github.com/pyrustic/litedbc/blob/master/tests/test_s...