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

Migration failed on existing database #266

New Issue
Closed
opened 2026-03-13 07:40:13 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-03-13 07:40:13 -05:00
Owner
Copy Link

Originally created by @MrKepzie on GitHub (Nov 23, 2024).

Running cli migrate fails on existing database because the fields are required but unset on existing accounts.
I understand that this is in beta, but shouldn't any added extra field be required=false ?
How am I supposed to go around this on my end ?

npx @better-auth/cli@latest migrate -y
(node:8687) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
ℹ  🔑 The migration will affect the following:                                                                                                                                            Better Auth
-> token, createdAt, updatedAt fields on session table.
-> accessTokenExpiresAt, refreshTokenExpiresAt, scope, createdAt, updatedAt fields on account table.
-> updatedAt fields on verification table.
⠋ migrating...node:internal/process/promises:289
            triggerUncaughtException(err, true /* fromPromise */);
            ^

error: column "createdAt" of relation "account" contains null values
Originally created by @MrKepzie on GitHub (Nov 23, 2024). Running cli migrate fails on existing database because the fields are required but unset on existing accounts. I understand that this is in beta, but shouldn't any added extra field be `required=false` ? How am I supposed to go around this on my end ? ``` npx @better-auth/cli@latest migrate -y (node:8687) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead. (Use `node --trace-deprecation ...` to show where the warning was created) ℹ 🔑 The migration will affect the following: Better Auth -> token, createdAt, updatedAt fields on session table. -> accessTokenExpiresAt, refreshTokenExpiresAt, scope, createdAt, updatedAt fields on account table. -> updatedAt fields on verification table. ⠋ migrating...node:internal/process/promises:289 triggerUncaughtException(err, true /* fromPromise */); ^ error: column "createdAt" of relation "account" contains null values ```
GiteaMirror commented 2026-03-13 07:40:14 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Nov 23, 2024):

If you are already using it in production, you should add the fields manually instead.

@Bekacru commented on GitHub (Nov 23, 2024): If you are already using it in production, you should add the fields manually instead.
GiteaMirror commented 2026-03-13 07:40:14 -05:00
Author
Owner
Copy Link

@MrKepzie commented on GitHub (Nov 23, 2024):

Could it be that the migrate tool prints the type of the fields that would be added aswell as their name ?

@MrKepzie commented on GitHub (Nov 23, 2024): Could it be that the migrate tool prints the type of the fields that would be added aswell as their name ?
GiteaMirror commented 2026-03-13 07:40:14 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Nov 23, 2024):

Yeah, it might not be a bad idea to show what fields need to be added, prior to migration, even if it fails. But for now, you can check the schema in the docs.https://www.better-auth.com/docs/concepts/database#core-schema

@Bekacru commented on GitHub (Nov 23, 2024): Yeah, it might not be a bad idea to show what fields need to be added, prior to migration, even if it fails. But for now, you can check the schema in the docs.https://www.better-auth.com/docs/concepts/database#core-schema
GiteaMirror commented 2026-03-13 07:40:15 -05:00
Author
Owner
Copy Link

@MrKepzie commented on GitHub (Nov 23, 2024):

ok thanks, as long as it's up to date it's fine!

@MrKepzie commented on GitHub (Nov 23, 2024): ok thanks, as long as it's up to date it's fine!
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#266
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?