Sure

Hello I want to pre-populate the database in my KMM project. I’m using SQLDelight. I have this implementation for the Android side.

actual fun Scope.createDriver(): SqlDriver {

    val context = androidContext()
    val fileName = "dbFileName"
    val database: File = context.getDatabasePath(fileName)

    if (!database.exists()) {
        val inputStream = context.assets.open(fileName)
        val outputStream = FileOutputStream(database.absolutePath)

        inputStream.use { input ->
            outputStream.use {
                input.copyTo(it)
            }
        }
    }

    return AndroidSqliteDriver(NoteDatabase.Schema, context, fileName)
}

I tried this code on iOS but it’s not working.

val path = "test.db"
val fileManager = NSFileManager.defaultManager

if (!fileManager.fileExistsAtPath(path)) {
    val bundlePath = MR.assets.balagh_ul_quran.url.path.toString()
    fileManager.copyItemAtPath(bundlePath, toPath = path, error = null)

}

return NativeSqliteDriver(NoteDatabase.Schema, path)

then tried this implementation:

actual fun Scope.createDriver(): SqlDriver {

    val databaseName = "test.db"
    val fileManager = NSFileManager.defaultManager

    val documentsDirectory = fileManager.URLsForDirectory(NSDocumentDirectory, inDomains = NSUserDomainMask).first() as NSURL
    val destinationURL = documentsDirectory.URLByAppendingPathComponent(databaseName)

    val bundlePath = MR.assets.balagh_ul_quran.url

    if (!fileManager.fileExistsAtPath(destinationURL?.path.toString())) {
        val response = try {
            if (destinationURL != null) {
                fileManager.copyItemAtURL(bundlePath, toURL = destinationURL, error = null)
            } else {

            }
        } catch (e: Exception) {
            showLog("catch:${e.message}")
        }

        println("myLog: $response")
    }

    return NativeSqliteDriver(NoteDatabase.Schema, destinationURL?.path.toString())
}

But nothing worked. Can anyone provide any sample app or docs something? thanks!

The file you try to use, does it only contains sql? And do you use the same sql code for Android and iOS? If so, you could simply put the sql code to your sqldelight files. Anything not marked with a query identifier is executed by default during schema creation.

First time using sqldelight. Question based off my other one above. I'm trying to put all of the sqldelight code in a single gradle module. Seems like I can't follow the sqldelight docs for android because I have just a pure java module right now and it's requiring a

Context

. should i just cave and make it an android gradle module? Should I just use the multiplatform docs instead?

I guess saying it out loud now again... I suppose I can't have sqldelight in a jvm module as im strictly tied to sqlite impl on android... right?

You could have the consumer of your module supply the driver

i guess i wanted a jvm module so i could write tests, but if i have the consumer of the module supply the driver then I guess I can't do that?

Your tests would supply the JVM sqlite driver

Or actually, I could have my :app module supply the android driver, and I could have my :persistence module have a test have the jvm driver

ah sweet. yeah same page. 🙏 Let me do that!

Need to create a PR to change these samples. Ryan Getzlaf? Really? 😂 lets get some Fleury in there

i have to abandon hockey player examples

they get stale after like a year

Ronald McDonald on the other hand... always great and stale 😂

cool. so thanks to the pointers everyone. I think i have a setup working where my persistence layer is a jvm only module. the module has tests that uses an in memory jdbc database 🦜

some interesting bits: 1. i thought i needed to find a separate dependency for jdbc since it wasn't importing in my test. didn't know that jdbc came out of the box. lol 2. turns out #1 was caused by a java version mismatch that i didnt find until i tried to actually build everything 3. my tests were initially failing because i didn't call

Database.Schema.create(driver)

which was just because my android code didn't have that. wonder why i need that on the jvm but not android? 4. in android land i know that its typically good to only keep one database object around as a singleton that DI'd everywhere. in the case of SQLDelight, I'm not sure what I should keep as singletons. There's the

Driver

,

Database

and

*Queries

. any tips on that?

oh probably I am thinking it wrong, since when served to host, everything runs in quickJs vm, it would want js impl for any references made, • there is no by default interop happening, where ever we do want to do, we must do by bridging and taking a ziplineService from host explicitly. if not everything should be avlbl within js. if true, just expanding my understanding, zipline also ships libs like kotlin stdlib for js everytime as well ?

I found this in the Block Android Software Engineer descriptions for Workflow and Espresso UI for testing. When I look at Workflow testing, I get coming soon. It going to be crazy mix.

Regarding sqldelight 2.0: I’m using it for Postgres dialect, and I noticed that generated files required r2dbc driver. I have added only jdbc one. I understand I need to add r2dc, but documentation does not mention it - am I doing something wrong?

If you have

generateAsync

enabled in your gradle config it will generate code for R2DBC. If you want to use JDBC you can just remove

generateAsync

.

I forgot I added it there - thanks. Does it mean I can remove jdbc from my classpath then?

If you're using R2DBC then yeah you can remove the JDBC dependency

Why is the logo for SqlDelight a sqldelight

It’s a database with many layers Eliezer.

😵‍💫

Wouldn't having layers make it an onion (or an ogre)?

Why is the use of slack threads discouraged? It seems like everyone is ignoring that anyway

Moshi life pro tip. I hope you love and hate this as much as I do. Need custom adapter behaviors but don't feel like wiring up the DI to get your adapter into the dagger graph? Just lie to it and hand write it! Moshi will reflect it into existence later!

@JsonClass(generateAdapter = true, generator = "hand-written")
sealed class ClientMessage {
  val type: String
    get() = this.javaClass.name

  companion object Unknown : ClientMessage()
}

@JsonClass(generateAdapter = true)
data class Launch(
    val request: JobRequest
) : ClientMessage()

@Keep
class ClientMessageJsonAdapter(private val moshi: Moshi) : JsonAdapter<ClientMessage>() {

  @Suppress("UNCHECKED_CAST")
  private val actual by lazy {
    PolymorphicJsonAdapterFactory.of(
        ClientMessage::class.java,
        "type",
    )
        .withSubtype(Launch::class.java, Launch::class.java.name)
        .withDefaultValue(ClientMessage.Unknown)
        .create(ClientMessage::class.java, emptySet(), moshi) as JsonAdapter<ClientMessage>
  }

  override fun fromJson(reader: JsonReader): ClientMessage? {
    return actual.fromJson(reader)
  }

  override fun toJson(writer: JsonWriter, value: ClientMessage?) {
    actual.toJson(writer, value)
  }
}