Shubham Singh
01/26/2023, 3:17 AMjw
01/26/2023, 3:19 AMjw
01/26/2023, 3:19 AMorg.xerial:sqlite-jdbc:3.40.0.0
which bundles the sqlite native libraryShubham Singh
01/26/2023, 3:20 AMjw
01/26/2023, 3:20 AMShubham Singh
01/26/2023, 3:21 AMShubham Singh
01/26/2023, 3:21 AMI useThanks for this suggestion.. I'll try it out 🙂which bundles the sqlite native libraryorg.xerial:sqlite-jdbc:3.40.0.0
Shubham Singh
01/26/2023, 4:37 AM.db
files on JVM and using them with SQLDelight?jw
01/26/2023, 4:37 AMjw
01/26/2023, 4:40 AMdb.kt
to omit the pathjw
01/26/2023, 4:40 AMjdbc:sqlite:in-memory:
or somethingShubham Singh
01/26/2023, 4:44 AM.db
file on the user's end and use it in SQLDelight. I'm going through your dodo example to understand how you did it. Looks like there already exists a 1.db
file, I'll now be trying to understand how that file was generated.jw
01/26/2023, 4:44 AMjw
01/26/2023, 4:45 AMTo generate a .db file from your latest schema, run the generateSqlDelightSchema task, which is available once you specify a schemaOutputDirectory, as described in the gradle.md. You should probably do this before you create your first migration.