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

[GH-ISSUE #2801] In Drizzle MySQL mode, wrong column types are generated #9354

New Issue
Closed
opened 2026-04-13 04:47:36 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-13 04:47:36 -05:00
Owner
Copy Link

Originally created by @hexwanderer on GitHub (May 27, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/2801

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

When using the generate command in CLI for drizzle MySQL, the outputted schema object is subtly wrong.

Auth object:

export const auth = betterAuth({
    database: drizzleAdapter(db, {
        provider: "mysql",
        usePlural: true,
    }),
    secret: env.BETTER_AUTH_SECRET,
    emailAndPassword: {
        enabled: true,
    },
    plugins: [bearer()],
    trustedOrigins: [env.CLIENT],
});

Generated file is:

export const users = mysqlTable("users", {
    id: varchar("id", { length: 36 }).primaryKey(),
    ...
});

export const accounts = mysqlTable("accounts", {
        ...
    userId: text("user_id", )
        .notNull()
        .references(() => users.id, { onDelete: "cascade" }),
});

This causes the error when running drizzle-kit push:

Error: Referencing column 'user_id' and referenced column 'id' in foreign key constraint 'accounts_user_id_users_id_fk' are incompatible.

I need to manually edit myself to:

export const sessions = mysqlTable("sessions", {
        ...
    userId: varchar("user_id", { length: 36 })
        .notNull()
        .references(() => users.id, { onDelete: "cascade" }),
});

Then the push works. I am using TiDB free tier if that's relevant.

Current vs. Expected behavior

Expected behavior would be for the CLI to generate varchar -> varchar references.

What version of Better Auth are you using?

1.2.8

Provide environment information

- OS: macOS 15.3.1

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

Backend

Auth config (if applicable)

export const auth = betterAuth({
    database: drizzleAdapter(db, {
        provider: "mysql",
        usePlural: true,
    }),
    secret: env.BETTER_AUTH_SECRET,
    emailAndPassword: {
        enabled: true,
    },
    plugins: [bearer()],
    trustedOrigins: [env.CLIENT],
});

Additional context

No response

Originally created by @hexwanderer on GitHub (May 27, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/2801 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce When using the generate command in CLI for drizzle MySQL, the outputted schema object is subtly wrong. Auth object: ```ts export const auth = betterAuth({ database: drizzleAdapter(db, { provider: "mysql", usePlural: true, }), secret: env.BETTER_AUTH_SECRET, emailAndPassword: { enabled: true, }, plugins: [bearer()], trustedOrigins: [env.CLIENT], }); ``` Generated file is: ```ts export const users = mysqlTable("users", { id: varchar("id", { length: 36 }).primaryKey(), ... }); export const accounts = mysqlTable("accounts", { ... userId: text("user_id", ) .notNull() .references(() => users.id, { onDelete: "cascade" }), }); ``` This causes the error when running drizzle-kit push: ```bash Error: Referencing column 'user_id' and referenced column 'id' in foreign key constraint 'accounts_user_id_users_id_fk' are incompatible. ``` I need to manually edit myself to: ```ts export const sessions = mysqlTable("sessions", { ... userId: varchar("user_id", { length: 36 }) .notNull() .references(() => users.id, { onDelete: "cascade" }), }); ``` Then the push works. I am using TiDB free tier if that's relevant. ### Current vs. Expected behavior Expected behavior would be for the CLI to generate varchar -> varchar references. ### What version of Better Auth are you using? 1.2.8 ### Provide environment information ```bash - OS: macOS 15.3.1 ``` ### Which area(s) are affected? (Select all that apply) Backend ### Auth config (if applicable) ```typescript export const auth = betterAuth({ database: drizzleAdapter(db, { provider: "mysql", usePlural: true, }), secret: env.BETTER_AUTH_SECRET, emailAndPassword: { enabled: true, }, plugins: [bearer()], trustedOrigins: [env.CLIENT], }); ``` ### Additional context _No response_
GiteaMirror added the locked label 2026-04-13 04:47:36 -05:00
GiteaMirror commented 2026-04-13 04:47:38 -05:00
Author
Owner
Copy Link

@Kinfe123 commented on GitHub (May 28, 2025):

Yeah this is more into the TiDB supporting foreign key constraints between the text and varchar. please refer here - https://docs.pingcap.com/tidb/stable/foreign-key/ but would look into something that can be make this easier.

<!-- gh-comment-id:2914566767 --> @Kinfe123 commented on GitHub (May 28, 2025): Yeah this is more into the TiDB supporting foreign key constraints between the text and varchar. please refer here - https://docs.pingcap.com/tidb/stable/foreign-key/ but would look into something that can be make this easier.
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#9354
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?