P
Prismaā€¢4w ago
Mas0n

Issue migrating a vector field

evelyn % npx prisma migrate dev
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "postgres", schema "public" at "aws-0-us-east-1.pooler.supabase.com:5432"

Error: P3006

Migration `20250331035432_add_calendar_subscription` failed to apply cleanly to the shadow database. 
Error:
ERROR: type "vector" does not exist
   0: sql_schema_connector::validate_migrations
           with namespaces=None
             at schema-engine/connectors/sql-schema-connector/src/lib.rs:364
   1: schema_core::state::DevDiagnostic
             at schema-engine/core/src/state.rs:275
evelyn % npx prisma migrate dev
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "postgres", schema "public" at "aws-0-us-east-1.pooler.supabase.com:5432"

Error: P3006

Migration `20250331035432_add_calendar_subscription` failed to apply cleanly to the shadow database. 
Error:
ERROR: type "vector" does not exist
   0: sql_schema_connector::validate_migrations
           with namespaces=None
             at schema-engine/connectors/sql-schema-connector/src/lib.rs:364
   1: schema_core::state::DevDiagnostic
             at schema-engine/core/src/state.rs:275
Would appreciate some help, I already reset my database
2 Replies
Prisma AI Help
Prisma AI Helpā€¢4w ago
You opted for speed from this bot. Let's conjure up an answer right now! I can help you with this migration error related to the vector type in Prisma. This is a common issue when working with PostgreSQL extensions like pgvector. The error message ERROR: type "vector" does not exist indicates that Prisma is trying to create a table with a vector field, but the PostgreSQL database doesn't recognize the vector type because the pgvector extension hasn't been properly installed or enabled in your database. Here are some steps to resolve this issue: 1. Enable the PostgreSQL Extensions preview feature in your schema.prisma file: 
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["postgresqlExtensions"]
}

datasource db {
  provider   = "postgresql"
  url        = env("DATABASE_URL")
  extensions = [pgvector(map: "vector")]
}
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["postgresqlExtensions"]
}

datasource db {
  provider   = "postgresql"
  url        = env("DATABASE_URL")
  extensions = [pgvector(map: "vector")]
}
2. Make sure your vector field is defined correctly using the Unsupported type: 
model YourModel {
  id        String                  @id @default(cuid())
  embedding Unsupported("vector")?  // or with dimensions: Unsupported("vector(1536)")
}
model YourModel {
  id        String                  @id @default(cuid())
  embedding Unsupported("vector")?  // or with dimensions: Unsupported("vector(1536)")
}
3. Create a migration that explicitly enables the pgvector extension at the beginning of your migration file. After running npx prisma migrate dev, open the generated migration file and ensure it has: 
-- CreateExtension
CREATE EXTENSION IF NOT EXISTS "vector";
-- CreateExtension
CREATE EXTENSION IF NOT EXISTS "vector";
If you're using Supabase (which appears to be the case from your connection URL), you might need to ensure that: 1. The pgvector extension is installed on your Supabase instance 2. Your database user has the necessary permissions to create extensions For Supabase specifically, you might need to manually enable the vector extension through the Supabase dashboard before attempting migrations. If you continue to face issues, you could try using the directUrl configuration in your datasource to bypass connection poolers: 
datasource db {
  provider  = "postgresql"
  url       = env("DATABASE_URL")
  directUrl = env("DIRECT_URL
")
  extensions = [vector]
}
datasource db {
  provider  = "postgresql"
  url       = env("DATABASE_URL")
  directUrl = env("DIRECT_URL
")
  extensions = [vector]
}
This issue is documented in several GitHub discussions, including Support for pg_vector and I can't migrate PostGIS tables. Let me know if you need further assistance with this issue! šŸ¤” Alright, thanks for letting us know that there's still some help needed. A team member will reply to you shortly. In the meantime, please let us know any additional info, questions, or which parts of the answer may need clarification.
Nurul
Nurulā€¢3w ago
Hey šŸ‘‹ Can you share the model which has the Vector field? Did you mark the vector column with Unsupported Type?

Did you find this page helpful?