Prisma Migrate - Drift detected error on each migrate run even when nothing changes in DB/Schema

Bug description

Reopening #5282 with only the drift detected issue.

I get drift detected error every time I run Prisma migrate dev command even without making a single change to my schema. I migrated my existing database to Prisma and introspected it. Also created an init migration using SQL dump so that my schema, migrations and database all are in sync. Everything works fine for me including migrations creation using prisma migrate but the drift detected comes up every time.

How to reproduce

Not sure. Have already shared my schema file earlier with @pimeys

Expected behavior

Shouldn’t get drift detected error since everything is in sync

Prisma information

Environment & setup

• OS: MacOS Catalina 10.15.1, Running inside docker node:14.15.4-alpine
• Database: PostgreSQL
• Node.js version: v14.15.4
• Prisma version:

prisma               : 2.17.0
@prisma/client       : 2.17.0
Current platform     : linux-musl
Query Engine         : query-engine 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/query-engine-linux-musl)
Migration Engine     : migration-engine-cli 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/migration-engine-linux-musl)
Introspection Engine : introspection-core 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/introspection-engine-linux-musl)
Format Binary        : prisma-fmt 3c463ebd78b1d21d8fdacdd27899e280cf686223 (at node_modules/@prisma/engines/prisma-fmt-linux-musl)
Studio               : 0.353.0
Preview Features     : createMany

[tomhoule]

Hi @codeslayer1 — @pimeys provided me with the schema and the migrations and I spent some time reproducing your issue. The problem is that your first migration redefines the Prisma migrations table. If you delete this part of the migration, the drift goes away:

CREATE TABLE IF NOT EXISTS public._prisma_migrations (
    id character varying(36) NOT NULL,
    checksum character varying(64) NOT NULL,
    finished_at timestamp with time zone,
    migration_name character varying(255) NOT NULL,
    logs text,
    rolled_back_at timestamp with time zone,
    started_at timestamp with time zone DEFAULT now() NOT NULL,
    applied_steps_count integer DEFAULT 0 NOT NULL
);

[codeslayer1]

Hey @tomhoule. This worked. Thanks a lot. Couldn’t have guessed this fix 😅