github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-06-02 04:16:38 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[drizzleAdapter] refresh a session won't update the updatedAt column #1246

New Issue
Closed
opened 2026-03-13 08:29:56 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-03-13 08:29:56 -05:00
Owner
Copy Link

Originally created by @ImSingee on GitHub (May 22, 2025).

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

  1. Create a new project, set session.updateAge to a short one (e.g. 1min) to reproduce the issue easily
  2. Sign in a user
  3. Wait for some time (more than session.updateAge), and get /api/auth/get-session to trigger a session refresh
  4. See the returned object (or the database). The expiresAt is updated, but the updatedAt is still the same as createdAt

Current vs. Expected behavior

The updatedAt should be updated automatically.

What version of Better Auth are you using?

1.2.8

Provide environment information

- OS: macOS & Linux

Which area(s) are affected? (Select all that apply)

Backend

Auth config (if applicable)

import { betterAuth } from "better-auth"
export const auth = betterAuth({
   database: drizzleAdapter(db, {
    provider: "pg",
  }),
  session: {
    expiresIn: 60 * 60 * 24 * 90, // 90 days
    updateAge: 60 * 1, // 1 minutes
  },
});

Additional context

This issue might also affect other tables.

While users can resolve it through manual database hook configuration, updatedAt is a built-in feature of better-auth and ideally should not require user intervention.

Originally created by @ImSingee on GitHub (May 22, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce 1. Create a new project, set session.updateAge to a short one (e.g. 1min) to reproduce the issue easily 2. Sign in a user 3. Wait for some time (more than session.updateAge), and get /api/auth/get-session to trigger a session refresh 4. See the returned object (or the database). The expiresAt is updated, but the updatedAt is still the same as createdAt ### Current vs. Expected behavior The updatedAt should be updated automatically. ### What version of Better Auth are you using? 1.2.8 ### Provide environment information ```bash - OS: macOS & Linux ``` ### Which area(s) are affected? (Select all that apply) Backend ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" export const auth = betterAuth({ database: drizzleAdapter(db, { provider: "pg", }), session: { expiresIn: 60 * 60 * 24 * 90, // 90 days updateAge: 60 * 1, // 1 minutes }, }); ``` ### Additional context This issue might also affect other tables. While users can resolve it through manual database hook configuration, `updatedAt` is a built-in feature of better-auth and ideally should not require user intervention.
GiteaMirror commented 2026-03-13 08:29:57 -05:00
Author
Owner
Copy Link

@devallibus commented on GitHub (May 22, 2025):

Can confirm, it is also happening on my end.

@devallibus commented on GitHub (May 22, 2025): Can confirm, it is also happening on my end.
GiteaMirror commented 2026-03-13 08:29:57 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (May 22, 2025):

PR -> #2747

@Bekacru commented on GitHub (May 22, 2025): PR -> #2747
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#1246
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?