[BUG]: Incorrect migration generation for constraints with schemas/databases in PostgreSQL

[buyna-gtn]

What version of drizzle-orm are you using?

0.30.10

What version of drizzle-kit are you using?

0.21.1

Describe the Bug

Drizzle kit is generating incorrect migrations, when adding composite unique constraint on new columns in existing PostgreSQL table. Columns were created inside the table without the unique constraint.

const user = pgTable(
  "user",
  {
    id: uuid("id").primaryKey().defaultRandom(),
    email: text("email").unique().notNull(),

    // Newly added columns
    firstName: text("first_name").notNull(),
    lastName: text("last_name").notNull(),
    //-------------------------------------
    role: userRole("role").notNull().default("member"),
    status: userStatus("status").notNull().default("active"),

    createdAt: timestamp("created_at").notNull().defaultNow(),
    updatedAt: timestamp("updated_at").notNull().defaultNow(),
  },
  (table) => ({
    nameUnq: unique().on(table.firstName, table.lastName),
  }),
);

GENERATED MIGRATION:

ALTER TABLE "user" ADD COLUMN "first_name" text NOT NULL;--> statement-breakpoint
ALTER TABLE "user" ADD COLUMN "last_name" text NOT NULL;

Expected behavior

Drizzle kit should generate composite unique constraint on first_name and last_name columns.

Environment & setup

No response