05nelsonm
commented
11 months ago Would like to also note here, the use of temporary databases. If passing an empty string to SQLite for the file path, it will create a "temporary" database. SQLite will act as an in-memory db, but dumps to a temp file when needed (which gets deleted upon connection closure).
Using :memory: means no dumps, ever.
So, a single static connection would need to be maintained in that instance as well. You can achieve a "temporary" database configuration with SQLiter by passing empty strings for DatabaseConfiguration.name, and DatabaseConfiguration.Extended.basePath, and then passing false for DatabaseConfiguration.inMemory.
`
SQLDelight Version
1.5.3+
Application Operating System
iOS, Native, etc
Describe the Bug
The in-memory mode of sqlite without a shared cache name allows only one connection. The sqldelight driver uses multiple connections. In earlier versions of sqliter, all in-memory connections were named, but that changed. You can skip the name on config, but that may cause issues with sqldelight.
Should investigate if that's actually an issue. If so, either modify the sqldelight driver to live with one connection, fail trying to use sqldelight in that mode with sqliter, or in some other way signal the issue. Mentioning it in docs is probably not enough.
For reference: https://github.com/touchlab/SQLiter/issues/7
Stacktrace
No response