Does migrateAndValidate migrate always to the latest version?

[MiguelSOliveira]

I'm trying to verify migrations using the test api, like so:

schemaVersion was updated from v8 to v9.

This test fails:

test('upgrade from v7 to v8', () async {
    final connection = await verifier.startAt(7);
    final db = MoorDb.connect(connection);
    await db.customStatement('PRAGMA schema_version = 7');
    await verifier.migrateAndValidate(db, 8, validateDropped: true);
  });

Output "From" and "to":
"Upgrading v7 to v9"

Because apparently, even though i specify in the migrateAndValidate 8 as the target version, it still migrates to v9? Is this the expected behavior?

[MiguelSOliveira]

it seems that the problem is here:

    await db.executor.ensureOpen(_DelegatingUser(expectedVersion, db));
    final actualSchema = await db.executor.collectSchemaInput();

IT uses v9 instead of v8 and I don't understand why.

[MiguelSOliveira]

Also worth noting that on schema_v7 and schema_v8, the new field does not exist (which is why the test is failing, because it expects this new column which was introduced in v9)

[MiguelSOliveira]

Which of these is the expectedVersion schema?

await db.executor.ensureOpen(_DelegatingUser(expectedVersion, db));
    final actualSchema = await db.executor.collectSchemaInput();

    // Open another connection to instantiate and extract the reference schema.
    final otherConnection = await startAt(expectedVersion);
    await otherConnection.executor.ensureOpen(_DelegatingUser(expectedVersion));
    final referenceSchema = await otherConnection.executor.collectSchemaInput();
    await otherConnection.executor.close();

Is it referenceSchema or actualSchema? Both use the expectedVersion?

What version I use in schemaVersion is used as the "to" variable...

Ex: when schemaVersion is set arbitrarily to 19 i get:

Upgrading v7 to v19
Migrating v7
Migrating v8
No migration available for v9
No migration available for v10
No migration available for v11
No migration available for v12
No migration available for v13
No migration available for v14
No migration available for v15
No migration available for v16
No migration available for v17
No migration available for v18

[MiguelSOliveira]

Hey @simolus3, I managed to track down the issue.

await db.customStatement('PRAGMA schema_version = 7');

I used to need this line, on a previous version because the verifier.startAt wasn't working. Now apparently it isn't needed anymore..

Still don't understand why this line would cause everything to break though.

[davidmartos96]

I don't thing that schema_version should be used to change the version, as that is used internally by Sqlite.
The times I've needed to force a migration in some of my tests I used the pragma user_version instead.
The schema_version could even cause corruption. Be aware of that.

https://www.sqlite.org/pragma.html#pragma_schema_version

[kuhnroyal]

Moor internally uses user_version even so the field in the database class is called schemaVersion. Don't mess with schema_version manually.