docs(pg): clarify account uniqueness for account lookup#13416
Open
DbibihOthmane wants to merge 1 commit into
Open
docs(pg): clarify account uniqueness for account lookup#13416DbibihOthmane wants to merge 1 commit into
DbibihOthmane wants to merge 1 commit into
Conversation
Document the expected uniqueness on account lookup fields used by the Pg adapter. This keeps the schema example aligned with getUserByAccount.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
@DbibihOthmane is attempting to deploy a commit to the authjs Team on Vercel. A member of the Team first needs to authorize it. |
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 PostgreSQL adapter resolves linked accounts by querying the
accountstable usingproviderandproviderAccountIdingetUserByAccount.However, the schema example does not enforce or document a uniqueness constraint on this pair. This allows duplicate rows for the same account, which does not match the adapter’s lookup behavior and can lead to ambiguous results.
This change clarifies that a unique constraint on
(provider, "providerAccountId")is expected for correct adapter behavior.🧢 Checklist
🎫 Affected issues
N/A