github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 15:42:09 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #568] Use of a custom user table name which cause the twoFactor table a bug #16954

New Issue
Closed
opened 2026-04-15 14:54:11 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-15 14:54:11 -05:00
Owner
Copy Link

Originally created by @Limerio on GitHub (Nov 17, 2024).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/568

Describe the bug
When you do a migration with the cli, you have the twoFactor plugin, and you update the user modelName option. That will cause an error : Table "user" does not exist

To Reproduce
Steps to reproduce the behavior:
I assumed that you have already configure the database

  1. Change the modelName of the user option to whatever you want
  2. Add in the plugins list the MFA plugin
  3. Do a migration

Expected behavior
The migration works as normal.

Desktop (please complete the following information):

  • OS: MacOS
  • Browser: Arc
  • Version: 1.69

Additional context
Add any other context about the problem here.

Originally created by @Limerio on GitHub (Nov 17, 2024). Original GitHub issue: https://github.com/better-auth/better-auth/issues/568 **Describe the bug** When you do a migration with the cli, you have the twoFactor plugin, and you update the user modelName option. That will cause an error : `Table "user" does not exist` **To Reproduce** Steps to reproduce the behavior: _I assumed that you have already configure the database_ 1. Change the `modelName` of the `user` option to whatever you want 2. Add in the plugins list the MFA plugin 3. Do a migration **Expected behavior** The migration works as normal. **Desktop (please complete the following information):** - OS: MacOS - Browser: Arc - Version: 1.69 **Additional context** Add any other context about the problem here.
GiteaMirror added the locked label 2026-04-15 14:54:11 -05:00
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 locked
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#16954
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?