4 replies

Latest CLI changes drizzle datetime fields from mode: 'timestamp' → mode: 'timestamp_ms'

@Better Auth i’m using drizzle + cloudflare D1 and i added some

user.additionalFields

user.additionalFields

to my config, so i ran

npx @better-auth/cli generate

npx @better-auth/cli generate

and all the existing datetime fields were changed from a unix timestamp in seconds to a unix timestamp in milliseconds. here’s a representative example extracted from

session

session

, with before:

    expiresAt: integer('expires_at', { mode: 'timestamp' }).notNull(),

    expiresAt: integer('expires_at', { mode: 'timestamp' }).notNull(),

and after:

    expiresAt: integer('expires_at', { mode: 'timestamp_ms' }).notNull(),

    expiresAt: integer('expires_at', { mode: 'timestamp_ms' }).notNull(),

the

createdAt

createdAt

updatedAt

updatedAt

also include new default/onupdate logic, which seems pretty straightforward. before:

    createdAt: integer('created_at', { mode: 'timestamp' }).notNull(),
    updatedAt: integer('updated_at', { mode: 'timestamp' }).notNull(),

    createdAt: integer('created_at', { mode: 'timestamp' }).notNull(),
    updatedAt: integer('updated_at', { mode: 'timestamp' }).notNull(),

and after:

    createdAt: integer('created_at', { mode: 'timestamp_ms' })
        .default(sql`(cast(unixepoch('subsecond') * 1000 as integer))`)
        .notNull(),
    updatedAt: integer('updated_at', { mode: 'timestamp_ms' })
        .$onUpdate(() => /* @__PURE__ */ new Date())
        .notNull(),

    createdAt: integer('created_at', { mode: 'timestamp_ms' })
        .default(sql`(cast(unixepoch('subsecond') * 1000 as integer))`)
        .notNull(),
    updatedAt: integer('updated_at', { mode: 'timestamp_ms' })
        .$onUpdate(() => /* @__PURE__ */ new Date())
        .notNull(),

i tried generating a drizzle migration based on the changes, and it doesn’t look like the existing timestamps are being migrated (no

SET createdAt = createdAt * 1000

SET createdAt = createdAt * 1000

or the like). here’s the excerpt for the

session

session

table:

INSERT INTO `__new_session`("active_organization_id", "active_team_id", "created_at", "expires_at", "id", "ip_address", "token", "updated_at", "user_agent", "user_id") SELECT "active_organization_id", "active_team_id", "created_at", "expires_at", "id", "ip_address", "token", "updated_at", "user_agent", "user_id" FROM `session`;--> statement-breakpoint
DROP TABLE `session`;--> statement-breakpoint
ALTER TABLE `__new_session` RENAME TO `session`;--> statement-breakpoint
CREATE UNIQUE INDEX `session_token_unique` ON `session` (`token`);--> statement-breakpoint

INSERT INTO `__new_session`("active_organization_id", "active_team_id", "created_at", "expires_at", "id", "ip_address", "token", "updated_at", "user_agent", "user_id") SELECT "active_organization_id", "active_team_id", "created_at", "expires_at", "id", "ip_address", "token", "updated_at", "user_agent", "user_id" FROM `session`;--> statement-breakpoint
DROP TABLE `session`;--> statement-breakpoint
ALTER TABLE `__new_session` RENAME TO `session`;--> statement-breakpoint
CREATE UNIQUE INDEX `session_token_unique` ON `session` (`token`);--> statement-breakpoint

is there application logic to ensure that i can make this change and everything will still work seemlessly?

Better Auth•5mo ago•

4 replies

acusti

Latest CLI changes drizzle datetime fields from mode: 'timestamp' → mode: 'timestamp_ms'

@Better Auth i’m using drizzle + cloudflare D1 and i added some

user.additionalFields

user.additionalFields

to my config, so i ran

npx @better-auth/cli generate

npx @better-auth/cli generate

and all the existing datetime fields were changed from a unix timestamp in seconds to a unix timestamp in milliseconds. here’s a representative example extracted from

session

session

, with before:

    expiresAt: integer('expires_at', { mode: 'timestamp' }).notNull(),

    expiresAt: integer('expires_at', { mode: 'timestamp' }).notNull(),

and after:

    expiresAt: integer('expires_at', { mode: 'timestamp_ms' }).notNull(),

    expiresAt: integer('expires_at', { mode: 'timestamp_ms' }).notNull(),

the

createdAt

createdAt

updatedAt

updatedAt

also include new default/onupdate logic, which seems pretty straightforward. before:

    createdAt: integer('created_at', { mode: 'timestamp' }).notNull(),
    updatedAt: integer('updated_at', { mode: 'timestamp' }).notNull(),

    createdAt: integer('created_at', { mode: 'timestamp' }).notNull(),
    updatedAt: integer('updated_at', { mode: 'timestamp' }).notNull(),

and after:

    createdAt: integer('created_at', { mode: 'timestamp_ms' })
        .default(sql`(cast(unixepoch('subsecond') * 1000 as integer))`)
        .notNull(),
    updatedAt: integer('updated_at', { mode: 'timestamp_ms' })
        .$onUpdate(() => /* @__PURE__ */ new Date())
        .notNull(),

    createdAt: integer('created_at', { mode: 'timestamp_ms' })
        .default(sql`(cast(unixepoch('subsecond') * 1000 as integer))`)
        .notNull(),
    updatedAt: integer('updated_at', { mode: 'timestamp_ms' })
        .$onUpdate(() => /* @__PURE__ */ new Date())
        .notNull(),

i tried generating a drizzle migration based on the changes, and it doesn’t look like the existing timestamps are being migrated (no

SET createdAt = createdAt * 1000

SET createdAt = createdAt * 1000

or the like). here’s the excerpt for the

session

session

table:

INSERT INTO `__new_session`("active_organization_id", "active_team_id", "created_at", "expires_at", "id", "ip_address", "token", "updated_at", "user_agent", "user_id") SELECT "active_organization_id", "active_team_id", "created_at", "expires_at", "id", "ip_address", "token", "updated_at", "user_agent", "user_id" FROM `session`;--> statement-breakpoint
DROP TABLE `session`;--> statement-breakpoint
ALTER TABLE `__new_session` RENAME TO `session`;--> statement-breakpoint
CREATE UNIQUE INDEX `session_token_unique` ON `session` (`token`);--> statement-breakpoint

INSERT INTO `__new_session`("active_organization_id", "active_team_id", "created_at", "expires_at", "id", "ip_address", "token", "updated_at", "user_agent", "user_id") SELECT "active_organization_id", "active_team_id", "created_at", "expires_at", "id", "ip_address", "token", "updated_at", "user_agent", "user_id" FROM `session`;--> statement-breakpoint
DROP TABLE `session`;--> statement-breakpoint
ALTER TABLE `__new_session` RENAME TO `session`;--> statement-breakpoint
CREATE UNIQUE INDEX `session_token_unique` ON `session` (`token`);--> statement-breakpoint

is there application logic to ensure that i can make this change and everything will still work seemlessly?

Latest CLI changes drizzle datetime fields from mode: 'timestamp' → mode: 'timestamp_ms'

Latest CLI changes drizzle datetime fields from mode: 'timestamp' → mode: 'timestamp_ms'

Similar Threads

Similar Threads

Similar Threads