Will work on this one

@AndriiSherman Sorry about the ping, but this is currently a blocker for me. Do you have a timeline?

I'm having the same problem with pgvector-node in drizzle. I've been just manually removing the quotes from the migration files. Not a huge deal once the specific column is in there and don't get modified, but definitely annoying.

"drizzle-orm": "0.29.4",
"drizzle-kit": "0.20.14",

Describe the Bug

import { vector } from "pgvector/drizzle-orm";

export const table = pgTable('table_name', {
  // ...
   embedding: vector("embedding", { dimensions: 3 }),
  // ...
});

The above table generates the following query:

CREATE TABLE IF NOT EXISTS "table_name" (
   "embedding" "vector(3)",
);

Expected behavior

CREATE TABLE IF NOT EXISTS "table_name" (
   "embedding" vector(3)
);

I have the same problem with a geography(Point,4326) typed column. When the migration file is generated drizzle-kit put double quotes around it like:

CREATE TABLE IF NOT EXISTS "table_name" (
   "location" "geography(Point,4326)" NOT NULL
);

This will raise an SQL exception saying that the type does not exist.

SQL Error [42704]: ERROR: type "geography(Point,4326)" does not exist

My temporary solution to take advantage of migrations on this specific project was to add a script that read the SQL files generated by drizzle-kit and remove the double quotes for this specific type.

{
    "drizzle:mig": "drizzle-kit migrate && tsx ./remove-pgsql-quotes.ts"
}

This solution solves part of the problem because I can use migrations for production deployment but I still cannot use the drizzle-kit push command while in development environment unless I edit the library source at node_modules.

Openned a pull request on this #2863