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

[PR #5162] [MERGED] docs: how to use non-public pg schemas with BA #5817

New Issue
Closed
opened 2026-03-13 12:37:31 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-13 12:37:31 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/5162
Author: @ping-maxwell
Created: 10/8/2025
Status: ✅ Merged
Merged: 10/8/2025
Merged by: @ping-maxwell

Base: canary ← Head: docs/pg-nonpublic-schema-better-auth

📝 Commits (2)

  • 5714628 docs: how to use non-public pg schemas with BA
  • 3a89ca4 chore: improve wording

📊 Changes

1 file changed (+20 additions, -0 deletions)

View changed files

📝 docs/content/docs/adapters/postgresql.mdx (+20 -0)

📄 Description

linear: https://linear.app/better-auth/issue/ENG-222/docs-document-how-to-use-non-public-postgresql-schemas-with-better
issue: https://github.com/better-auth/better-auth/issues/4452

Summary by cubic

Add docs on using a non-default PostgreSQL schema with Better Auth. Explains setting search_path via ALTER USER or connection URI (URL-encoded) and the need for schema creation and permissions; addresses Linear ENG-222 and GitHub #4452.

🔄 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/5162 **Author:** [@ping-maxwell](https://github.com/ping-maxwell) **Created:** 10/8/2025 **Status:** ✅ Merged **Merged:** 10/8/2025 **Merged by:** [@ping-maxwell](https://github.com/ping-maxwell) **Base:** `canary` ← **Head:** `docs/pg-nonpublic-schema-better-auth` --- ### 📝 Commits (2) - [`5714628`](https://github.com/better-auth/better-auth/commit/5714628dec70f7804d6a47d2136c0b83b1a44d9c) docs: how to use non-public pg schemas with BA - [`3a89ca4`](https://github.com/better-auth/better-auth/commit/3a89ca491f25a68bce80f7b5437731a3472ff6d9) chore: improve wording ### 📊 Changes **1 file changed** (+20 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/adapters/postgresql.mdx` (+20 -0) </details> ### 📄 Description linear: https://linear.app/better-auth/issue/ENG-222/docs-document-how-to-use-non-public-postgresql-schemas-with-better issue: https://github.com/better-auth/better-auth/issues/4452 <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Add docs on using a non-default PostgreSQL schema with Better Auth. Explains setting search_path via ALTER USER or connection URI (URL-encoded) and the need for schema creation and permissions; addresses Linear ENG-222 and GitHub #4452. <!-- 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-03-13 12:37:31 -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#5817
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?