feat: add options object where you can specify a schema

[jlvdh]

☕️ Reasoning

The @auth/kysely-adapter currently depends on the tables to be configured in postgres. But it's good practice to add the tables in their own schema (eg auth.User, auth.Session, etc.) This PR would enable the configuration of a schema that is used for all the necessary tables by using: KyselyAdapter(db, {schemaName: "auth"})

Interested to hear if this type of feature would be eligible to merge in the project?

🧢 Checklist

• Documentation
• Tests
• Ready to be merged

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
auth-docs	❌ Failed (Inspect)			Aug 9, 2024 9:25am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
next-auth-docs	⬜️ Ignored (Inspect)	Visit Preview		Aug 9, 2024 9:25am

[vercel]

@jlvdh is attempting to deploy a commit to the authjs Team on Vercel.

A member of the Team first needs to authorize it.

[ndom91]

Yeah so in general we do something similar in most other adapters. Ideally we wouldn't have an implicit link between what you name something in your DB schema manually adn the name we expect in the kysely adapter code..

I'm not familiar with Kysely, but can you explicitly define the schemas and pass them to the Kysely instance? Like we do in the Drizzle adapter

[jlvdh]

@ndom91 Thanks for the reply.

Kysely doesn't seem to use models like Drizzle. In Kysely you write your own migrations. So passing the schema and table names would be in string format.

KyselyAdapter(db, {schemaName: "auth"})

Could simply be added using withSchema

ie: https://github.com/nextauthjs/next-auth/pull/11344/files#diff-8f2587157000f269c1784f539508271ebb924ca9b7f5a5fdccd02fe2682c56e5R70

For further customisation of the table names we could do something like:

KyselyAdapter(db, {schemaName: "auth", accountTable: "account", userTable: "user" .. etc })

[jlvdh]

Added tests and docs now too