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

[GH-ISSUE #799] Column name in snake_case #8441

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

Originally created by @emersonlaurentino on GitHub (Dec 7, 2024).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/799

Just like usePlural, would be nice if the database drizzleAdapter config has an useSnakeCase to generate the column names in snake_case.

Example:

betterAuth({
  database: drizzleAdapter(db, {
    provider: "sqlite",
    usePlural: true,
    useSnakeCase: true,
  }),
});

the schema is like that:

// ...
  expiresAt: integer("expires_at", { mode: "timestamp" }).notNull(),
// ...
Originally created by @emersonlaurentino on GitHub (Dec 7, 2024). Original GitHub issue: https://github.com/better-auth/better-auth/issues/799 Just like `usePlural`, would be nice if the database drizzleAdapter config has an `useSnakeCase` to generate the column names in snake_case. Example: ```tsx betterAuth({ database: drizzleAdapter(db, { provider: "sqlite", usePlural: true, useSnakeCase: true, }), }); ``` the schema is like that: ```tsx // ... expiresAt: integer("expires_at", { mode: "timestamp" }).notNull(), // ... ```
GiteaMirror added the lockedduplicate labels 2026-04-13 03:30:42 -05:00
GiteaMirror commented 2026-04-13 03:30:44 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Dec 7, 2024):

for drizzle, prisma... snake case should be handled by the adapter instead. Better Auth only interacts with the orm layer. meaning in your case it only cares what you named your keys not the actual mapping in your db.

<!-- gh-comment-id:2524953721 --> @Bekacru commented on GitHub (Dec 7, 2024): for drizzle, prisma... snake case should be handled by the adapter instead. Better Auth only interacts with the orm layer. meaning in your case it only cares what you named your keys not the actual mapping in your db.
GiteaMirror commented 2026-04-13 03:30:44 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Dec 7, 2024):

we plan to support it for the builtin Kysely adapter but there is open issue at #410 already

<!-- gh-comment-id:2524954131 --> @Bekacru commented on GitHub (Dec 7, 2024): we plan to support it for the builtin Kysely adapter but there is open issue at #410 already
GiteaMirror commented 2026-04-13 03:30:44 -05:00
Author
Owner
Copy Link

@emersonlaurentino commented on GitHub (Dec 7, 2024):

for drizzle, prisma... snake case should be handled by the adapter instead. Better Auth only interacts with the orm layer. meaning in your case it only cares what you named your keys not the actual mapping in your db.

but when I run the migrate command by CLI, the map is in camelCase, that's my point.

<!-- gh-comment-id:2525100767 --> @emersonlaurentino commented on GitHub (Dec 7, 2024): > for drizzle, prisma... snake case should be handled by the adapter instead. Better Auth only interacts with the orm layer. meaning in your case it only cares what you named your keys not the actual mapping in your db. but when I run the migrate command by CLI, the map is in camelCase, that's my point.
GiteaMirror commented 2026-04-13 03:30:45 -05:00
Author
Owner
Copy Link

@svaraborut commented on GitHub (Dec 15, 2024):

Yes, the migrate command is used for the builtin Kysely which as mentioned by @Bekacru does not yet support snake_case and is tracked separately in https://github.com/better-auth/better-auth/issues/410 . Other adapters have their respective configuration for casing.

<!-- gh-comment-id:2543516106 --> @svaraborut commented on GitHub (Dec 15, 2024): Yes, the `migrate` command is used for the builtin Kysely which as mentioned by @Bekacru does not yet support snake_case and is tracked separately in https://github.com/better-auth/better-auth/issues/410 . Other adapters have their respective configuration for casing.
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 duplicate 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#8441
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?