[BUG]: drizzle-kit migrate fail "applying migrations...error: column "authorid" does not exist" #2423

Weixuanf · 2024-06-02T15:25:46Z

What version of `drizzle-orm` are you using?

0.31.0

What version of `drizzle-kit` are you using?

0.22.1

Describe the Bug

npx drizzle-kit migrate throws error and fail to create any table in my postgres db , while npx drizzle-kit push throws error but can create tables in my postgres db

Before I upgrade to 0.22.1, this issue doesn't occur, I was at:
drizzle-kit: v0.21.2
drizzle-orm: v0.30.10

After upgrading to drizzle-kit: v0.22.1, this issue happened.
drizzle-kit: v0.22.1
drizzle-orm: v0.31.0

$ npx drizzle-kit migrate
drizzle-kit: v0.22.1
drizzle-orm: v0.31.0

No config path provided, using default path
Reading config file '/Users/weixuan/git/peach-icon/drizzle.config.ts'
Using 'pg' driver for database querying
[⣟] applying migrations...error: column "authorid" does not exist
    at /Users/weixuan/git/peach-icon/node_modules/drizzle-kit/bin.cjs:77692:15
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at <anonymous> (/Users/weixuan/git/peach-icon/node_modules/src/pg-core/dialect.ts:89:7)
    at NodePgSession.transaction (/Users/weixuan/git/peach-icon/node_modules/src/node-postgres/session.ts:155:19)
    at PgDialect.migrate (/Users/weixuan/git/peach-icon/node_modules/src/pg-core/dialect.ts:82:3)
    at migrate (/Users/weixuan/git/peach-icon/node_modules/src/node-postgres/migrator.ts:10:2) {
  length: 98,
  severity: 'ERROR',
  code: '42703',
  detail: undefined,
  hint: undefined,
  position: undefined,
  internalPosition: undefined,
  internalQuery: undefined,
  where: undefined,
  schema: undefined,
  table: undefined,
  column: undefined,
  dataType: undefined,
  constraint: undefined,
  file: 'indexcmds.c',
  line: '1884',
  routine: 'ComputeIndexAttrs'
}

Expected behavior

No response

Environment & setup

No response

The text was updated successfully, but these errors were encountered:

CamTheGoblin · 2024-06-02T16:00:09Z

I just ran into a similar issue that happens with drizzle-kit push as well. appears to be an issue with the setting up indexes. As a simple example:

export const user = pgTable(
  "user",
  {
    id:serial("id").primaryKey(),
    testId: string("testId"),
  },
  (table) => ({
    testIdx: index("testidx").on(table.testId),
  }),
);

This generates the error: "error: column "testid" does not exist
If I change the testId column name to all lower case to match the error message, then things work testId: string("testid")

Additionally index does not seem to like dashes in the column name, so testId: string("test-id") generates this error : "error: syntax error at or near "-" "

Weixuanf · 2024-06-02T16:25:33Z

I just ran into a similar issue that happens with drizzle-kit push as well. appears to be an issue with the setting up indexes. As a simple example:
export const user = pgTable(
  "user",
  {
    id:serial("id").primaryKey(),
    testId: string("testId"),
  },
  (table) => ({
    testIdx: index("testidx").on(table.testId),
  }),
);
This generates the error: "error: column "testid" does not exist If I change the testId column name to all lower case to match the error message, then things work testId: string("testid")

Additionally index does not seem to like dashes in the column name, so testId: string("test-id") generates this error : "error: syntax error at or near "-" "

oh interesting..but I don't want to use all lower case column name.. i hope drizzle team can fix this soon. I really need to use the new features in drizzle 0.31.0 to create compound index with desc() inside the index().on()...but this bug is preventing me to upgrate to 0.31.0

thanks very much for your response! this is helpful information for me!

mandarzope · 2024-06-03T05:47:38Z

This happens with PostgreSQL. By default, PostgreSQL converts all tokens to lowercase unless they are wrapped in double quotes. The solution is to keep your keys in the required case; however, database columns need to be lowercase for PostgreSQL.

Weixuanf · 2024-06-03T19:31:57Z

This happens with PostgreSQL. By default, PostgreSQL converts all tokens to lowercase unless they are wrapped in double quotes. The solution is to keep your keys in the required case; however, database columns need to be lowercase for PostgreSQL.

Oh! Thanks for the explanation. It seems it is best practice to use snake_case for column names in postgres (https://wiki.postgresql.org/wiki/Don't_Do_This#Don.27t_use_upper_case_table_or_column_names). I didn't know this before hehe. This makes sense then. However, the previous version of drizzle (kit 21.0 , orm 30.10) worked fine on this.

Anyway I'll change to use snake case to follow the best practice.
Thanks for the info!

ThomasAunvik · 2024-06-04T10:56:39Z

Related Issue: #2413

AndriiSherman · 2024-06-07T15:15:10Z

Should be fixed in [email protected]

Weixuanf · 2024-06-07T15:19:27Z

Thank you for fixing this!!

…

________________________________ From: Andrii Sherman ***@***.***> Sent: Friday, June 7, 2024 11:15:32 PM To: drizzle-team/drizzle-orm ***@***.***> Cc: Weixuan Fu ***@***.***>; Author ***@***.***> Subject: Re: [drizzle-team/drizzle-orm] [BUG]: drizzle-kit migrate fail "applying migrations...error: column "authorid" does not exist" (Issue #2423) Should be fixed in ***@***.*** — Reply to this email directly, view it on GitHub<#2423 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEMEEOK233YHQF5ZIVYF6Y3ZGHFBJAVCNFSM6AAAAABIVE2KTKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJVGA2DMNJZGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

AlejandroSanchez90 · 2024-08-09T01:53:23Z

im getting this same error but because a type enum

export const fileTypeEnum = pgEnum('fileType', ['image/jpeg', 'application/pdf'])

this is the table

export const files = pgTable('files', {
  id: text('id').primaryKey(),
  roId: text('roId').notNull(),
  name: text('name').notNull(),
  key: text('key').notNull(),
  url: text('url').notNull(),
  type: fileTypeEnum('type').notNull(),
  createdAt: timestamp('createdAt').defaultNow().notNull()
})

and this is the error

[⡿] applying migrations...PostgresError: type "filetype" does not exist
    at ErrorResponse (/home/alejandro/.dev/toyota-ro/node_modules/drizzle-kit/bin.cjs:79677:27)
    at handle (/home/alejandro/.dev/toyota-ro/node_modules/drizzle-kit/bin.cjs:79454:7)
    at Socket.data (/home/alejandro/.dev/toyota-ro/node_modules/drizzle-kit/bin.cjs:79277:9)
    at Socket.emit (node:events:517:28)
    at addChunk (node:internal/streams/readable:368:12)
    at readableAddChunk (node:internal/streams/readable:341:9)
    at Readable.push (node:internal/streams/readable:278:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
    at TCP.callbackTrampoline (node:internal/async_hooks:128:17) {
  severity_local: 'ERROR',
  severity: 'ERROR',
  code: '42704',
  file: 'parse_type.c',
  line: '270',
  routine: 'typenameType'
}

Jonathan-R0 · 2025-01-14T16:54:26Z

im getting this same error but because a type enum

export const fileTypeEnum = pgEnum('fileType', ['image/jpeg', 'application/pdf'])

this is the table

export const files = pgTable('files', {
  id: text('id').primaryKey(),
  roId: text('roId').notNull(),
  name: text('name').notNull(),
  key: text('key').notNull(),
  url: text('url').notNull(),
  type: fileTypeEnum('type').notNull(),
  createdAt: timestamp('createdAt').defaultNow().notNull()
})

and this is the error

[⡿] applying migrations...PostgresError: type "filetype" does not exist
    at ErrorResponse (/home/alejandro/.dev/toyota-ro/node_modules/drizzle-kit/bin.cjs:79677:27)
    at handle (/home/alejandro/.dev/toyota-ro/node_modules/drizzle-kit/bin.cjs:79454:7)
    at Socket.data (/home/alejandro/.dev/toyota-ro/node_modules/drizzle-kit/bin.cjs:79277:9)
    at Socket.emit (node:events:517:28)
    at addChunk (node:internal/streams/readable:368:12)
    at readableAddChunk (node:internal/streams/readable:341:9)
    at Readable.push (node:internal/streams/readable:278:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
    at TCP.callbackTrampoline (node:internal/async_hooks:128:17) {
  severity_local: 'ERROR',
  severity: 'ERROR',
  code: '42704',
  file: 'parse_type.c',
  line: '270',
  routine: 'typenameType'
}

Same here! any fixes? :(

ManadayM · 2025-01-15T16:55:43Z

@Jonathan-R0

TL;DR

Delete your migrations folder and generate the migrations again. It fixed the issue for me.

Detailed

I faced the same error today. In my case, I initially missed the export keyword in front of my enum. The generated migrations did not include the enums and that was obvious.

To fix that, I prefixed the export keyword to my enums and generated the migrations. It generated the migration file for the enum but it was the last file (003_xxx.sql). In my case, file 002_xxx.sql was referring to this enum. I believe it was the root cause.

I simply deleted the migrations directory and generated new migrations. It fixed the issue.

Hope it helps.

ndubosq · 2025-01-15T18:18:06Z

@Jonathan-R0

TL;DR

Delete your migrations folder and generate the migrations again. It fixed the issue for me.

Detailed

I faced the same error today. In my case, I initially missed the export keyword in front of my enum. The generated migrations did not include the enums and that was obvious.

To fix that, I prefixed the export keyword to my enums and generated the migrations. It generated the migration file for the enum but it was the last file (003_xxx.sql). In my case, file 002_xxx.sql was referring to this enum. I believe it was the root cause.

I simply deleted the migrations directory and generated new migrations. It fixed the issue.

Hope it helps.

Worked for me by adding export, ty !

Weixuanf added the bug Something isn't working label Jun 2, 2024

AndriiSherman closed this as completed Jun 7, 2024

beermonsterdota mentioned this issue Jun 14, 2024

[BUG]: drizzle-kit generate creates broken SQL for postgres when creating compound primary key #2514

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[BUG]: drizzle-kit migrate fail "applying migrations...error: column "authorid" does not exist" #2423

[BUG]: drizzle-kit migrate fail "applying migrations...error: column "authorid" does not exist" #2423

Weixuanf commented Jun 2, 2024 •

edited

Loading

CamTheGoblin commented Jun 2, 2024 •

edited

Loading

Weixuanf commented Jun 2, 2024 •

edited

Loading

mandarzope commented Jun 3, 2024

Weixuanf commented Jun 3, 2024

ThomasAunvik commented Jun 4, 2024

AndriiSherman commented Jun 7, 2024

Weixuanf commented Jun 7, 2024 via email

AlejandroSanchez90 commented Aug 9, 2024

Jonathan-R0 commented Jan 14, 2025

ManadayM commented Jan 15, 2025 •

edited

Loading

ndubosq commented Jan 15, 2025

[BUG]: drizzle-kit migrate fail "applying migrations...error: column "authorid" does not exist" #2423

[BUG]: drizzle-kit migrate fail "applying migrations...error: column "authorid" does not exist" #2423

Comments

Weixuanf commented Jun 2, 2024 • edited Loading

What version of drizzle-orm are you using?

What version of drizzle-kit are you using?

Describe the Bug

Expected behavior

Environment & setup

CamTheGoblin commented Jun 2, 2024 • edited Loading

Weixuanf commented Jun 2, 2024 • edited Loading

mandarzope commented Jun 3, 2024

Weixuanf commented Jun 3, 2024

ThomasAunvik commented Jun 4, 2024

AndriiSherman commented Jun 7, 2024

Weixuanf commented Jun 7, 2024 via email

AlejandroSanchez90 commented Aug 9, 2024

Jonathan-R0 commented Jan 14, 2025

ManadayM commented Jan 15, 2025 • edited Loading

ndubosq commented Jan 15, 2025

Weixuanf commented Jun 2, 2024 •

edited

Loading

What version of `drizzle-orm` are you using?

What version of `drizzle-kit` are you using?

CamTheGoblin commented Jun 2, 2024 •

edited

Loading

Weixuanf commented Jun 2, 2024 •

edited

Loading

ManadayM commented Jan 15, 2025 •

edited

Loading