fix(se): Include duplicate indices (w/ different names) in migrations w/o drift #4894
Conversation
This file contains 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
…in migrations related: - prisma/prisma#6873 - #1904 - #4885
CodSpeed Performance ReportMerging #4894 will not alter performanceComparing Summary
|
WASM Query Engine file Size
|
SevInf
approved these changes
May 30, 2024
SevInf
requested changes
May 30, 2024
|
Closing this for now, as a fix is for thoertical bug that have not been reported yet by anyone and it turned fix is way more complicated than it is worth for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Handle indices on same columns with different names without ignoring in migrations
You can find a write-up further explaining the bug here
related: