The glitch originated from alterations made during the removal of old memory model support. The
SqlDriver underwent a change, adopting a regular
MutableMap without any locking mechanism. This rendered the map non-thread-safe, particularly problematic in scenarios with concurrent database operations.
The much-anticipated SQLDelight 2.0.1 has now been released, including a fix for the critical bug mentioned above.
Our recommendation: If you’re currently using version
2.0.0, we strongly suggest upgrading to
2.0.1 to pick up this fix. If you have not yet migrated to
2.0.0, then updating will require code changes, but may still be worth it.
Additionally, version 2.0.1 brings various other fixes. Explore the release notes here. Don’t miss out on the improvements!