3 replies

dates in sqlite not being evaluated, causing "Invalid Date"

    expiresAt: int("expires_at", { mode: "timestamp" })
      .notNull()
      .$defaultFn(() => new Date(Date.now() + 1000 * 60 * 60 * 24 * 365)),
    createdAt: int("created_at", { mode: "timestamp" })
      .notNull()
      .default(sql`CURRENT_TIMESTAMP`),

    expiresAt: int("expires_at", { mode: "timestamp" })
      .notNull()
      .$defaultFn(() => new Date(Date.now() + 1000 * 60 * 60 * 24 * 365)),
    createdAt: int("created_at", { mode: "timestamp" })
      .notNull()
      .default(sql`CURRENT_TIMESTAMP`),

I have the following columns in my sqlite table,

for some reason the

expiresAt

expiresAt

column works fine, when being read, its being evaluated as an actual date, and is saved in the database as an UNIX timestamp,

however, the createdAt column is being saved as an actual ISO string date, but upon quering it shows

INVALID DATE

INVALID DATE

, why is it?

Drizzle Team•2y ago•

3 replies

bun

dates in sqlite not being evaluated, causing "Invalid Date"

    expiresAt: int("expires_at", { mode: "timestamp" })
      .notNull()
      .$defaultFn(() => new Date(Date.now() + 1000 * 60 * 60 * 24 * 365)),
    createdAt: int("created_at", { mode: "timestamp" })
      .notNull()
      .default(sql`CURRENT_TIMESTAMP`),

    expiresAt: int("expires_at", { mode: "timestamp" })
      .notNull()
      .$defaultFn(() => new Date(Date.now() + 1000 * 60 * 60 * 24 * 365)),
    createdAt: int("created_at", { mode: "timestamp" })
      .notNull()
      .default(sql`CURRENT_TIMESTAMP`),

I have the following columns in my sqlite table,

for some reason the

expiresAt

expiresAt

INVALID DATE

INVALID DATE

, why is it?

dates in sqlite not being evaluated, causing "Invalid Date"

Similar Threads

dates in sqlite not being evaluated, causing "Invalid Date"

Similar Threads

Similar Threads

Similar Threads