nextauthjs / nextauthjs/next-auth
Database Model Consistentcy
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 28.4k
- Forks
- 4k
- PR merge metrics
- No merged PRs in 30d
Description
What is the improvement or update you wish to see?
PostgreSQL Adapter page has tables created with plural names.
Drizzle ORM Adapter page schema.ts has database tables created with singular names.
I wish they were more consistent.
Is there any context that might help us understand?
Why was this an issue for me?
Initially I was trying out the Drizzle solution because I appreciate the drizzle-kit migration functions. But then I ran into some edge runtime issues and couldn't figure it out. I turned to PG adapter, hoping to get a simpler solution. That's when I found out the table definitions are different.
Does the docs page already exist? Please link to it.
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the PostgreSQL Adapter page and the Drizzle ORM Adapter page, especially the schema.ts table definitions. Determine the consistent table-naming convention to use, update the affected documentation examples, and verify both pages show matching table names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, typescript
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100