You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are wondering if guarding accesses to our SQLDelight calls with a lock is necessary or useful.
We’re using the SQLite driver on Android and native and from what we can observe, concurrent access to the DB looks to be safe, or at least it’s the case when a transaction is involved. On Android for instance we can see threads going through a lock here.
Our impression is that SQLDelight isn’t doing anything in particular about thread safety, so ultimately it depends on the underlying DBMS - is that fair to say?
In general, any guidance about this topic is appreciated - and perhaps this would deserve a paragraph in the documentation (apologies if I missed it)?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi!
We are wondering if guarding accesses to our SQLDelight calls with a lock is necessary or useful.
We’re using the SQLite driver on Android and native and from what we can observe, concurrent access to the DB looks to be safe, or at least it’s the case when a transaction is involved. On Android for instance we can see threads going through a lock here.
Our impression is that SQLDelight isn’t doing anything in particular about thread safety, so ultimately it depends on the underlying DBMS - is that fair to say?
In general, any guidance about this topic is appreciated - and perhaps this would deserve a paragraph in the documentation (apologies if I missed it)?
Beta Was this translation helpful? Give feedback.
All reactions