Set tables in auth not public
Is it possible to set an option for better-auth to create the tables under
auth instead of public in postgresql?6 Replies
One option would be to set the default schema for the PostgreSQL user you plan to use before generating/migrating the schema:
Given a better-auth database user 'authuser' and a schema 'auth':
ALTER USER authuser SET SEARCH_PATH TO auth;
Another way to set this (again before generating/migrating the better-auth schema) is within the connectionString that you are using with your better-auth config by appending '?option=-c search_path=<schema_name>' to the connection URI :
connectionString: [existing postgresql connecting string]?option=-c search_path=auth
For both these approaches, make sure the PostgreSQL schema exists and the PostgreSQL user has permissions to use it.
thanks, will try this out
I don't remember with javascript/typescript PostgreSQL drivers, but you may need to escape the space and equal characters in the connection URI:
connectionString: [existing postgresql connecting string]?option=-c%20search_path%3Dauth
@chumpo I use Drizzle with Better Auth and I just manually change the default table schemas that Better Auth generates to point to an
auth schema I defined with Drizzle.@MaveriX89 that is definitely a solid approach for using a custom ORM schema within better-auth, but - if used with PostgreSQL - would not change what PostgreSQL schema the objects were created in and would default to them being created in the public schema (short a previous database/user customization with the PostgreSQL environment) unless a pgSchema object from "drizzle-orm/pg-core" was used in combination with the Drizzle pgTable objects.
The schema referenced in the OP question was an 'auth' Postgresql schema as opposed to the default use of the 'public' PostgreSQL schema to store better-auth database objects.
The schema referenced in the OP question was an 'auth' Postgresql schema as opposed to the default use of the 'public' PostgreSQL schema to store better-auth database objects.
marking this as solved!
Thanks @rtmorgan
and thanks @MaveriX89 for the suggestion but Im not using an orm