String default for integer timestamps?

Hey folks, I'm using Drizzle with SQLite on CloudFlare D1. Using the following column schema:

createdAt: integer("created_at", { mode: "timestamp" }).default(sql`CURRENT_TIMESTAMP`),

createdAt: integer("created_at", { mode: "timestamp" }).default(sql`CURRENT_TIMESTAMP`),

createdAt: integer("created_at", { mode: "timestamp" }).default(sql`CURRENT_TIMESTAMP`),

createdAt: integer("created_at", { mode: "timestamp" }).default(sql`CURRENT_TIMESTAMP`),

From the D1 database viewer I am seeing that Drizzle creates values that look like this

2024-01-03 03:55:45

2024-01-03 03:55:45

2024-01-03 03:55:45

2024-01-03 03:55:45, whereas values inserted via direct SQL are integers properly e.g.

1703894400

1703894400

1703894400

1703894400. In addition, the string values show up as

NULL

NULL

in Drizzle Studio. Could I be doing something wrong or have I encountered a bug?

Yuvaraj•1/3/24, 5:15 AM

I think you should use like this
createdAt :timestamp('columnname').defaultNow()

xeon06OP•1/8/24, 12:46 AM

SQLite doesn't have a timestamp type

xeon06OP•1/8/24, 12:46 AM

I'm starting to think this is a bug

Angelelz•1/8/24, 12:51 AM

SQLite? Isn't D1 Postgres?

xeon06OP•1/8/24, 12:53 AM

No sir

xeon06OP•1/8/24, 12:53 AM

https://orm.drizzle.team/docs/get-started-sqlite#cloudflare-d1

Drizzle ORM - next gen TypeScript ORM

Drizzle ORM is a lightweight and performant TypeScript ORM with developer experience in mind.

xeon06OP•1/8/24, 12:57 AM

https://github.com/drizzle-team/drizzle-orm/issues/1769

GitHub

[BUG]: Incorrect default value of integer timestamp fields with D1 ...

What version of drizzle-orm are you using? 0.29.2 What version of drizzle-kit are you using? 0.20.8 Describe the Bug Using CloudFlare D1, when inserting rows, columns with this type: createdAt: int...

Angelelz•1/8/24, 1:20 AM

My bad, I'll shut up

String default for integer timestamps?

Similar Threads

Similar Threads

Similar Threads