Regression in prisma migrate

I’ve noticed a regression in Prisma migrate. It worked fine in version 2.16, but later versions seem to have this issue.

Ran with version 2.19.0

: prisma migrate dev
Running node v14.16.0 (npm v6.14.11)
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "reviews.sqlite" at "file:../reviews.sqlite"

⚠️  Warnings:

  • You are about to drop the column `vendor` on the `products` table, which still contains 16 non-null values.

✔ Are you sure you want create and apply this migration? Some data will be lost. … yes
✔ Name of migration … remove vendor
Error: Database error: Timed out during query execution.
   0: migration_core::commands::apply_migrations::Applying migration
           with migration_name="20210401145435_remove_vendor"
             at migration-engine/core/src/commands/apply_migrations.rs:72
   1: migration_core::api::ApplyMigrations
             at migration-engine/core/src/api.rs:75

After rolling back to version 2.16.0. I can re-run the same migration without error.

: npx prisma migrate dev --preview-feature
Running node v14.16.0 (npm v6.14.11)
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "reviews.sqlite" at "file:../reviews.sqlite"

The following migration(s) have been applied:

migrations/
  └─ 20210401145435_remove_vendor/
    └─ migration.sql


Everything is now in sync.

Bug description

Prisma migrate fails with a timeout error

How to reproduce

Modify an existing table with prisma migrate.

Environment & setup

• OS: Ubuntu
• Database: SQLite
• Node.js version: 14
• Prisma version: 2.16, 2.19

[internalfx]

Tried it again with prisma 2.20.1

I tried adding the column back. Basically, prisma migrate is completely broken for versions > 2.16

: prisma migrate dev
Running node v14.16.0 (npm v6.14.11)
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "reviews.sqlite" at "file:../reviews.sqlite"

✔ Name of migration … add vendor
Error: Database error
Timed out during query execution.
   0: migration_core::commands::apply_migrations::Applying migration
           with migration_name="20210401155700_add_vendor"
             at migration-engine/core/src/commands/apply_migrations.rs:71
   1: migration_core::api::ApplyMigrations
             at migration-engine/core/src/api.rs:73

[pantharshit00]

Thanks for the reproduction repo @internalfx . I can confirm this.

(Internal note: For reproduction, clone the repo and run migrate).