Drift Detected: "Changed the `vector` extension" error without changes to Prisma Schema/DB about prisma HOT 11 OPEN

Solved it for my case. Idk how the prisma shadow db works but I had a feeling this had to with extensions versions. So I wrote my own migration like this:

CREATE EXTENSION IF NOT EXISTS vector;
ALTER EXTENSION vector UPDATE TO '0.5.0';

Because I knew my version was 0.5.0 by doing:

SELECT * from pg_extension;

Then I got this error messaage:

Migration `0_init` failed to apply cleanly to the shadow database. 
Error:
ERROR: extension "vector" has no update path from version "0.5.1" to version "0.5.0"
   0: schema_core::state::DevDiagnostic
             at schema-engine/core/src/state.rs:267

So it did seem like a version problem. So I went into my db and did

ALTER EXTENSION vector UPDATE TO '0.5.1';

And there it was, drift is gone.

from prisma.

I was able to temporarily resolve the issue by commenting out:

  // previewFeatures = ["postgresqlExtensions"]

and

// extensions = [vector]

from prisma.

+1 I'm having the same error!!!

from prisma.

having the same error

from prisma.

Same - does it refer to the new PSQL update?

from prisma.

It must be related to this same issue. Several people in the thread mentioned the same error as yours.

#18442

from prisma.

also facing this, working on Ubuntu 20.04 LTS

from prisma.

Same here

from prisma.

Still having this issue

from prisma.

Same issue here

from prisma.

For people that still have an issue not related to versions, another issue can be that the introspected databases declared the extensions on particular schemas, for example, i had an issue with citext :

[*] Changed the `citext` extension

My initial migration was generating :

CREATE EXTENSION IF NOT EXISTS "citext";

I decided to pg_dump the original database :

CREATE EXTENSION IF NOT EXISTS "citext" WITH SCHEMA "pg_catalog";

I just replaced the line in my 0_init migration, the warning was gone and my schema in sync 🍾

from prisma.