"The driver you are using does not support the new state management."

[domarp-j]

Hello,

I'm running an application that uses db-migrate-pg@0.3.1, which has db-migrate-base@1.5.3 as a dependency.

Our compilation process for local devleopment runs two migrations: one set of base migrations to build our PostgreSQL schema, and another set of migrations under the scope dev to add some seed data to the database.

Before today, our migrations ran fine. However, we're now seeing the following message in our logs:

[WARN] The driver you are using does not support the new state management. Please raise an issue in the repository of your driver maintainer

Our data now fails to seed because the dev-scoped migration is running our base migrations a second time. Because the migrations already ran in the past, the second run fails and never gets to the seed migrations further down the line.

We did not update any packages. Is there something I am missing? I can provide additional data if requested.

Thanks!

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[wzrdtales]

no nothing. the new beta tag was accidentially released instead of the stable branch and the new version checks the drivers for compatibility. This is nothing you will have to worry about, this functionality will be just skipped in the new version. There is nothing really blocking that is known until know that would raise an issue with the new version, so you could continue using it, but the last stable was 0.11.x.

the newest db-migrate-pg driver is compatible with the newest db-migrate version though. the major version bump was due to breaking the node js compatibility level. Before 1.x.x the db-migrate-pg driver still supported < 8 now it is only >= 8.

[wzrdtales]

the behaviour you're describing later however sounds wrong

Our data now fails to seed because the dev-scoped migration is running our base migrations a second time. Because the migrations already ran in the past, the second run fails and never gets to the seed migrations further down the line.

what do you mean with it runs the base migrations a second time? Which commands did you issue?

[domarp-j]

@wzrdtales Ah that makes sense. We use Docker to run our application, postgres DB, and other services locally. As part of the build process for the application's container, we install db-migrate globally (in the image's Dockerfile). I hardcoded the version to v0.11.11, which fixed the seeding issue. Thank you!

what do you mean with it runs the base migrations a second time? Which commands did you issue?

When we spin up the Docker containers for our application and postgres DB, we do the following:

• First, we run a set of base migrations with db-migrate up to run every migration under the migrations/ directory in our repo. These migrations set the schema for our postgres DB.
• Once those migrations succeed, we run the migrations for a specific scope depending on the build context. In dev, we run db-migrate up:dev to run everything in the migrations/dev/ directory. These migrations add seed data necessary for local development.

When we build the application's Docker image and globally install the latest stable version of db-migrate (v0.11.11), the above migrations work as expected.

However, when we were unintentionally installing the latest beta version, we would see the "driver you are using does not support new state management" warning message, and db-migrate up:dev would run the base migrations again. The second base migration run would fail, and the seeding migration would never run as a result.

[wzrdtales]

ok thanks for the information, I will try to reproduce this behaviour.