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 #9091] Drizzle adapter: allow overriding supportsUUIDs on PostgreSQL for explicit user ids from hooks #28593

New Issue
Closed
opened 2026-04-17 20:02:07 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-17 20:02:07 -05:00
Owner
Copy Link

Originally created by @dakaii on GitHub (Apr 10, 2026).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/9091

Problem

On PostgreSQL the Drizzle adapter sets supportsUUIDs: true. The adapter factory then treats UUID ids as database-generated and input transforms can omit explicit id values on create, even when using forceAllowId. Apps that insert a related row in databaseHooks.user.create.before and must reuse the same UUID for ba_user.id need to pass supportsUUIDs: false.

Proposal

Add optional supportsUUIDs to DrizzleAdapterConfig, defaulting to current behavior: config.supportsUUIDs ?? (provider === "pg").

PR

See linked PR.

Originally created by @dakaii on GitHub (Apr 10, 2026). Original GitHub issue: https://github.com/better-auth/better-auth/issues/9091 ## Problem On PostgreSQL the Drizzle adapter sets `supportsUUIDs: true`. The adapter factory then treats UUID ids as database-generated and input transforms can omit explicit `id` values on `create`, even when using `forceAllowId`. Apps that insert a related row in `databaseHooks.user.create.before` and must reuse the same UUID for `ba_user.id` need to pass `supportsUUIDs: false`. ## Proposal Add optional `supportsUUIDs` to `DrizzleAdapterConfig`, defaulting to current behavior: `config.supportsUUIDs ?? (provider === "pg")`. ## PR See linked PR.
GiteaMirror added the database label 2026-04-17 20:02:07 -05:00
GiteaMirror commented 2026-04-17 20:02:09 -05:00
Author
Owner
Copy Link

@hrougier commented on GitHub (Apr 12, 2026):

Looks like a duplicate of #9056?

<!-- gh-comment-id:4230512970 --> @hrougier commented on GitHub (Apr 12, 2026): Looks like a duplicate of #9056?
GiteaMirror commented 2026-04-17 20:02:09 -05:00
Author
Owner
Copy Link

@dakaii commented on GitHub (Apr 13, 2026):

@hrougier oh right. #9056 might fix the bug I encountered. I'll close my PR.

<!-- gh-comment-id:4233508641 --> @dakaii commented on GitHub (Apr 13, 2026): @hrougier oh right. #9056 might fix the bug I encountered. I'll close my PR.
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 database
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#28593
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?