A modern programming language that makes developers happier.

kotlinlang

does anyone know if you need 1 database per thread when using SQL Delight on native?

this comment leads me to believe the answer is no:
```// In reality the database and driver above should be created a single time
// and passed around using your favourite dependency injection/service locator/singleton pattern.```

if you are using any of the reactive apis (rxjava, flow) then you would need one database for the entire application

other than that there are no restrictions, its all immutable

On native, you absolutely should not try to create multiple connections outside of what SQLDelight would create. In the best case they’ll just block each other, but it won’t be any faster.

That statement is only maybe not true if you’ve got a bunch of threads reading, but haven’t tried to optimize that

i am just making sure I don't need one DB/driver per thread

Oh wait nvm. Yeah SQLDelight is supposed to handle this transparently

You definitely don’t need one per thread