This repository has been archived by the owner on Sep 2, 2022. It is now read-only.
Add validations and extra warnings to deploy when updating relations #2334
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
also remove @model directive from tests and @migrationValue from directiveDefinitions
…e back relation might be optional
…ards the same modelB
add error when adding singular optional back relation field but there are already multiple occurrences in existing data
will be fixed in a separate PR
do4gr
changed the title
|
Thanks guys!! Looking forward to try this out 😍 Do you have an ETA on when this is going to be released? |
|
@emmenko We have a bi-weekly release cycle for Prisma. The next release is scheduled for Tuesday next week. |
This was referenced Jan 16, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Do not strictly require a relation directive to appear twice anymore. https://github.com/graphcool/prisma/issues/1569 ,
Add a validation when adding an omitted back relation later. (If it's a to one relation the omitted side can only be in one relation in existing data.)
Add an error if we can not determine which relation operations to take after a schema change. Add a hint to provide relation directives or advance in steps. https://github.com/graphcool/prisma/issues/1836
Added tests for a case described here that was already fixed. https://github.com/graphcool/prisma/issues/1944
Fixes https://github.com/graphcool/prisma/issues/1569 , https://github.com/graphcool/prisma/issues/1836