A modern programming language that makes developers happier.

kotlinlang

If I connect to a SQLite DB in Exposed and use the same `Database` instance in separate transactions in two separate threads... I would expect to see uncommitted reads and similar. But I can't seem to reproduce that with a test. Does Exposed do something to ensure isolation?

Example:
- SQLite connection code: <https://gitlab.com/timmc/cavern/-/blob/isotest/spelunk/src/main/kotlin/org/timmc/spelunk/SQLite3.kt>
- Unit test that (I think) demonstrates isolation: <https://gitlab.com/timmc/cavern/-/blob/isotest/spelunk/src/test/kotlin/org/timmc/spelunk/IsolationTest.kt>

I'm under the impression that Exposed only creates one connection here, and that SQLite (in its default configuration) allows concurrent transactions on the same connection to see changes made by each other.

However, I wrote this test to try to read from one thread after another thread wrote, but before the transaction closed (using latches) and it passes but I don't understand why. :-)

I'm not an expert of SQLite but afaik the multithreaded code normally works only with a single connection (<https://www.sqlite.org/threadsafe.html>).

I believe that when that page talks about "safety" it's referring to classic thread-safety (preventing memory corruption, etc.) rather than transactional isolation.