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

[PR #6060] docs: clarify database mapping #23315

New Issue
Open
opened 2026-04-15 21:37:30 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-15 21:37:30 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/6060
Author: @okisdev
Created: 11/18/2025
Status: 🔄 Open

Base: main ← Head: docs/clarify-database-mapping

📝 Commits (3)

  • 6bf8e4e docs: clarify database mapping
  • cee383c Merge branch 'canary' into docs/clarify-database-mapping
  • 976b288 Merge branch 'canary' into docs/clarify-database-mapping

📊 Changes

2 files changed (+93 additions, -3 deletions)

View changed files

📝 docs/content/docs/concepts/database.mdx (+58 -3)
📝 docs/content/docs/reference/faq.mdx (+35 -0)

📄 Description

This PR adds more details information to clarify database mapping.

This PR closes #6059.

Summary by cubic

Clarified how field mapping works: the fields config only changes database column names, while your code always uses the original camelCase fields. Added examples, an info callout, and an FAQ entry to reduce confusion when using snake_case schemas.

Written for commit 976b2886af. Summary will update automatically on new commits.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/6060 **Author:** [@okisdev](https://github.com/okisdev) **Created:** 11/18/2025 **Status:** 🔄 Open **Base:** `main` ← **Head:** `docs/clarify-database-mapping` --- ### 📝 Commits (3) - [`6bf8e4e`](https://github.com/better-auth/better-auth/commit/6bf8e4ee1a70abe24e3205b115d5be463eb1e4c2) docs: clarify database mapping - [`cee383c`](https://github.com/better-auth/better-auth/commit/cee383c4cc9c9c29247eb3ba4bf4119d7d31f0be) Merge branch 'canary' into docs/clarify-database-mapping - [`976b288`](https://github.com/better-auth/better-auth/commit/976b2886affbce611561c34d15cf868281a7855a) Merge branch 'canary' into docs/clarify-database-mapping ### 📊 Changes **2 files changed** (+93 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/concepts/database.mdx` (+58 -3) 📝 `docs/content/docs/reference/faq.mdx` (+35 -0) </details> ### 📄 Description This PR adds more details information to clarify database mapping. This PR closes #6059. <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Clarified how field mapping works: the fields config only changes database column names, while your code always uses the original camelCase fields. Added examples, an info callout, and an FAQ entry to reduce confusion when using snake_case schemas. <sup>Written for commit 976b2886affbce611561c34d15cf868281a7855a. Summary will update automatically on new commits.</sup> <!-- End of auto-generated description by cubic. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-15 21:37:30 -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 pull-request
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#23315
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?