docs: fix MySQL Prisma account relation - #13473
Open
KariMuhammad wants to merge 2 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
@KariMuhammad is attempting to deploy a commit to the authjs Team on Vercel. A member of the Team first needs to authorize it. |
KariMuhammad
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
☕️ Reasoning
The MySQL Prisma schema contains two inconsistencies in the relationship between
UserandAccount:userIdis required, but the correspondinguserrelation is optional (User?).userIdhas an@uniqueconstraint, which prevents a user from linking multiple provider accounts despiteUser.accountsbeing anAccount[].This PR:
User?toUser.@uniquefromAccount.userId.This aligns the MySQL example with the PostgreSQL, SQLite, and MongoDB examples and correctly models the intended one-to-many relationship.
🧢 Checklist
🎫 Affected issues
Fixes #13472
📌 Resources