Add a capability for transactional mutations #80
Merged
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
paf31
reviewed
Jan 10, 2024
paf31
reviewed
Jan 10, 2024
|
@0x777 Could you please add your notes regarding the GraphQL/engine side of things here? |
paf31
reviewed
Jan 22, 2024
paf31
reviewed
Jan 23, 2024
paf31
reviewed
Jan 23, 2024
paf31
approved these changes
Jan 23, 2024
soupi
changed the title
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.
This PR encodes the support a connector offers wrt mutations in types.
It introduces a new capability,
mutation, to signal whether the connector supports mutations, and a field inMutationCapabilities,transactional, to signal whether the connector support running multiple mutations in a single transaction.Additional discussion on Slack: https://hasurahq.slack.com/archives/C065TFX2V2Q/p1702996285519119