So, you need to grab the version from the old db and set it manually in the new db, then you'd avoid the migration on sqldelight start. I'm making the assumption that sqldelight is trying to create a table that already exists from your migration process (correct?)
Yeah Kevin it looks like it is trying to create a table when I return NativeSqliteDriver(DatabaseConfiguration)
which is done after the migration process. I'm assuming the issue is the way I'm setting the version.
Thanks for the example Jake, going to take a look at it and see if I can apply it to our logic