Meanwhile, to enable the pgvector extension on your supported postgresql DB provider (like Supabase) through Prisma, the following schema.prisma can be used:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["postgresqlExtensions"]  // Enable the postgresqlExtensions. Currently in preview
}

datasource db {
  provider   = "postgresql"
  url        = env("DATABASE_URL")
  directUrl  = env("DIRECT_DATABASE_URL")
  extensions = [pgvector(map: "vector", schema: "extensions")]  // Add the pgvector extension
}
...

With the above, running npx prisma migrate dev --name "add_pgvector_extension" should generate and apply a migration with migration.sql containing the following:

CREATE EXTENSION IF NOT EXISTS "vector" WITH SCHEMA "extensions";

You can then use vector fields in your model schema by using:

model sample {
    embedding            Unsupported("vector")?
}

Hopefully the vector field type will become supported in a future Prisma version and we could use:

model sample {
    embedding            vector?
}

Support for pg_vector #18442

Description

Problem

Suggested solution

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Support for `pg_vector` #18442