A non-empty migration sqm file gets translated into an empty migration in kotlin

Runtime Environment SQLDelight version: 1.2.1 Application OS: Android

Describe the bug Adding a new migration file 6.sqm results in an empty section in the kotlin migrate script.

$ cat 6.sqm
import com.mycelium.wapi.wallet.fio.FioName;

CREATE TABLE IF NOT EXISTS FioKnownNames(
    name TEXT AS FioName PRIMARY KEY
);
$ cat WalletDBImpl.kt
...
      if (oldVersion <= 5 && newVersion > 5) {
        driver.execute(null, "ALTER TABLE EthAccountBacking ADD COLUMN internalValue TEXT;", 0)
      }
      if (oldVersion <= 6 && newVersion > 6) {
      }
    }
  }
}
...

From the discussion below: deriveSchemaFromMigrations was not set.

The not-so-surprising stacktrace:

2020-09-29 22:57:34.545 9952-9952/com.mycelium.testnetwallet.debug E/SQLiteLog: (1) no such table: FioKnownNames in "SELECT name
    FROM FioKnownNames"
2020-09-29 22:57:34.548 9952-9952/com.mycelium.testnetwallet.debug E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.mycelium.testnetwallet.debug, PID: 9952
    java.lang.RuntimeException: Unable to start activity ComponentInfo{com.mycelium.testnetwallet.debug/com.mycelium.wallet.activity.send.ManualAddressEntry}: android.database.sqlite.SQLiteException: no such table: FioKnownNames (code 1 SQLITE_ERROR): , while compiling: SELECT name
    FROM FioKnownNames

Expected behavior

Compile time error over the not allowed “AS FioName” part or kotlin output ignoring the “AS FioName” part.

[Giszmo]

I removed the types and it works. The bug-part on the library’s side is just that it silently generates an empty migration that leads to runtime crashes instead of throwing a compiletime error.

I updated name and description.

[AlecStrong]

sweet thanks