Problem

When using a custom PostgreSQL schema (e.g., auth instead of public), the CLI generate command outputs Drizzle schema using pgTable():

export const user = pgTable("user", {...});

Instead of using Drizzle's pgSchema() for explicit schema qualification:

const authSchema = pgSchema("auth");
export const user = authSchema.table("user", {...});

Current Workaround

The docs recommend using search_path at connection time:

connectionString: "postgres://...?options=-c search_path=auth"

This works for runtime queries, but the generated Drizzle schema doesn't reflect the actual database structure. This causes confusion and potential issues with drizzle-kit migrations.

Expected Behavior

If Better Auth detects a custom search_path in the database connection (or via a CLI flag), the generate command should output:

import { pgSchema } from "drizzle-orm/pg-core";

const authSchema = pgSchema("auth");

export const user = authSchema.table("user", {...});
export const session = authSchema.table("session", {...});
// etc.

Proposed Solutions

1. Auto-detect: If the CLI config has a real database connection, detect search_path and generate accordingly
2. CLI flag: Add --pg-schema auth flag to explicitly specify the schema
3. Config option: Add schema: "auth" option to the Drizzle adapter config

Environment

• Better Auth version: 1.4.x
• Database: PostgreSQL
• ORM: Drizzle

Related Docs

• PostgreSQL Adapter - Non-default schema
• CLI - Generate command

The docs mention custom schema support, but it only applies to migrate (Kysely) and runtime queries, not the generate command output for Drizzle users.