I notice, on Android, sqldelight grabs a writeable...

# squarelibraries

[Mark]

I notice, on Android, sqldelight grabs a writeable database when passed in a SupportSQLiteOpenHelper but what if the database is read-only (as in, you never want to modify it)? Are there any best practices/optimizations for opening such a database? I know there are some cases where readableDatabase returns a non-null value when writeableDatabase returns null, so there could be cases where it makes more sense to call readableDatabase . A nasty workaround is to override the helper so that the result of readableDatabase is returned when writeableDatabase is called. https://github.com/cashapp/sqldelight/blob/51e0621abe103761717d3d9078dcde3734ad8c0[…]ain/java/com/squareup/sqldelight/android/AndroidSqliteDriver.kt

[jw]

Is this hypothetical? If no, file a bug. We can add a parameter to only take a readable database

[Mark]

It’s documented behaviour though I don’t know the likelihood/circumstances https://stackoverflow.com/a/11751696/444761

[Mark]

https://github.com/cashapp/sqldelight/issues/2163

[Mark]

Further to my question from 4.5 years ago, these PRAGMAs are relevant according to Claude:

PRAGMA query_only = ON
PRAGMA cache_size = cacheSize // about 1.5x db file size
PRAGMA temp_store = MEMORY

[Mark]

I had to drop the query_only pragma because of rare cases where a simple query would lead to a read-only exception.