fix(qe) Don't use native upserts with nested selection #3377
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
Closed
garrensmith
force-pushed
the
fix/native-updates
branch
from
8ff5166
to
cedebc5
Compare
|
Merging as I assume we were waiting for passing tests, and all are passing now. So we can wake up with a freshly baked dev version tomorrow. |
Jolg42
pushed a commit
that referenced
this pull request
Nov 9, 2022
(cherry picked from commit 379f9d3)
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.
If an upsert uses a selection with nested models in the response then do not use native upserts
This fixes prisma/prisma#16196