DT
Drizzle Team•3w ago
chocolatkey

Possible bug in kit when using magic sql

I've found what could possibly be a bug in drizzle-kit, but before I file an issue, I wanted to check if anyone else has had this issue: I have a column such as 
created_at: timestamp("created_at").default(sql`CURRENT_TIMESTAMP`).notNull()
created_at: timestamp("created_at").default(sql`CURRENT_TIMESTAMP`).notNull()
in my MySQL schema definitions, which is valid. However when trying to use drizzle-kit's "Drizzle runner", the schema definition becomes 
createdAt: timestamp("created_at", { mode: 'string' }).default(CURRENT_TIMESTAMP).notNull()
createdAt: timestamp("created_at", { mode: 'string' }).default(CURRENT_TIMESTAMP).notNull()
and refuses to run because CURRENT_TIMESTAMP is not defined (CURRENT_TIMESTAMP also has error highlighting in the read-only editor of the schema in the UI). Is this a bug, or am I doing something wrong?
No description
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?