duplicate column name about drift HOT 5 CLOSED

Can you show the migration? Is it the latest one? Are you doing anything except adding the new column?
My best guess (but this requires more information either way) is that something in the migration goes wrong after that ALTER TABLE statement already ran. In that case, drift won't store the new version number and will try to re-run the migration afterwards, causing the error you're seeing. Do you see any other drift-related errors on the same devices that might indicate something with the migrations going wrong?

from drift.

Can you show the migration? Is it the latest one? Are you doing anything except adding the new column? My best guess (but this requires more information either way) is that something in the migration goes wrong after that ALTER TABLE statement already ran. In that case, drift won't store the new version number and will try to re-run the migration afterwards, causing the error you're seeing. Do you see any other drift-related errors on the same devices that might indicate something with the migrations going wrong?

Thank you for your help. I've identified the issue causing the problem. My database's latest version is 4, but I reinstalled an older version of my app and kept the database file, which downgraded the database version to 3. However, the 'speed' column wasn't deleted during this process. When I reinstalled the newest version of the app, it tried to add the 'speed' column again. To fix this, I should either add a statement for downgrading or check if the column exists before attempting an upgrade.

from drift.

Wondering, how can we check if the column exists before executing migration? I got the same issue the other day

from drift.

This PR contains code to check which columns currently exist in a database table. I'm not sure about merging it as I think the check should ideally be unnecessary in well-written migrations, but perhaps it's helpful as a pointer if you need that logic.

from drift.

Thanks, that would be amazing to have! I came up with something similar but it seems to be now wrong compared to your solution (didn't know about readNullable)

extension on Migrator {
  Future<bool> columnExists(String name, String table) async {
    // check if column exists
    final tableInfo = await database.customSelect('PRAGMA table_info(${table})').get();
    final column = tableInfo.firstWhereOrNull(
      (e) => e.read<String>('name') == name,
    );

    return column != null;
  }
}

from drift.