fix: exclude partial unique indexes from DMMF unique fields#5792
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (4)
WalkthroughThis PR adds detection and filtering logic for partial unique indexes in DMMF output. A new method identifies partial unique constraints on scalar fields, and the DMMF builder excludes partial indexes from uniqueness reporting to prevent incorrect Changes
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Hi @jacek-prisma. Please review these changes! Thank you. |
Merging this PR will not alter performance
Comparing Footnotes
|
Closes #5791
Summary
@@uniquewithwhereclause) from DMMFuniqueFieldsanduniqueIndexesisUnique: falsefor single-field partial unique constraintsis_partial_unique()method toScalarFieldWalkerContext
Partial unique constraints don't guarantee uniqueness across all rows, so generating
findUniqueinput types for them is incorrect. This fix ensures Prisma Client treats partial unique indexes as regular indexes rather than unique constraints.Related: prisma/prisma#29282
Summary by CodeRabbit
New Features
Tests