they must not be run on main. all of the APIs shou...

# multiplatform

[jw]

they must not be run on main. all of the APIs should be using Default as, well, a default.

[Daniele B]

I did not encounter problems running them on Dispatchers.Main, so I was assuming simple queries could be run there.

[Kris Wong]

as a best practice we do not perform any file or network IO on the main thread

[jw]

if you're using Android then turn on strict mode and your app will kindly crash when you do this

[Daniele B]

Is there any way to setup SqlDelight to automatically generate functions that run on WithContext(Dispatchers.Default) ?

[jw]

no

[jw]

if you use the built-in Flow extension that is the default behavior

[Daniele B]

do you also use Dispatchers.Default for reading a value from MultiplatformSettings?

[kevin.cianfarini]

You probably want some sort of abstraction (like a repository?) that ensures all network and database operations are main safe. Retrofit, for example, is main safe, however SQLDelight doesn’t expose first class suspend functions.

[jw]

i don't know what MultiplatformSettings is

[kpgalligan]

MultiplatformSettings would best be answered by @russhwolf I see there's a coroutines extension I've never played with, so the answer I was typing was wrong.

[russhwolf]

Settings doesn't do anything with dispatchers normally and lets the platforms APIs it delegates to handle threading (or not) when they write to disk. If you use the new experimental coroutines extensions and convert your Settings to a SuspendSettings (or ObservableSettings to FlowSettings), then you can pass a dispatcher for it to run on which will default to Dispatchers.Default. Most people probably aren't doing that though because those interfaces really only exist to make it easier to interop with androidx.datastore which nobody is using yet