[BUG]: Default value in array generating wrong migration file

[Aaditya-23]

What version of drizzle-orm are you using?

0.28.0

What version of drizzle-kit are you using?

0.19.12

Describe the Bug

This is my drizzle schema.

export const responses = pgTable('responses', {
  id: uuid('id').defaultRandom().primaryKey(),
  response: uuid('user_response').array().default([]).notNull(),
  isCorrect: boolean('is_correct'),
  userTestId: uuid('user_test_id')
    .references(() => userTests.id)
    .notNull(),
  questionId: uuid('question_id')
    .references(() => questions.id)
    .notNull(),
  createdAt: timestamp('created_at').defaultNow().notNull(),
})

Migrations look like this

CREATE TABLE IF NOT EXISTS "responses" (
	"id" uuid PRIMARY KEY DEFAULT gen_random_uuid() NOT NULL,
	"user_response" uuid[] DEFAULT  NOT NULL,
	"is_correct" boolean,
	"user_test_id" uuid NOT NULL,
	"question_id" uuid NOT NULL,
	"created_at" timestamp DEFAULT now() NOT NULL
);

Expected behavior

Whereas user_response column should be like

`"user_response" uuid[] DEFAULT '{}' NOT NULL,`

Environment & setup

I am using Next13, vercel postgres and turborepo.

[Aaditya-23]

Hey team @AndriiSherman any updates on this issue? I am unable to use db push because of this issue and I don't want migration files in my codebase.

[DevTobias]

I think you could use the magic sql operator to avoid this issue:

{
  response: uuid('user_response').array().default(sql`'{}'`).notNull(),
}

[AndriiSherman]

Should be fixed in drizzle-kit0.24.0
Please check release notes before updating