-
Notifications
You must be signed in to change notification settings - Fork 2.8k
allow specifying a list of columns that can be inserted (close #250) #917
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or 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
Contributor
|
Review app available at: https://hge-ci-pull-917.herokuapp.com |
0x777
previously approved these changes
Oct 30, 2018
21 tasks
karthikvt26
previously approved these changes
Nov 2, 2018
Contributor
karthikvt26
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Console changes LGTM
Contributor
|
Review app available at: https://hge-ci-pull-917.herokuapp.com |
Resolve Conflicts: server/src-lib/Hasura/GraphQL/Resolve/Insert.hs
…engine into issue-250-insert-cols
0x777
approved these changes
Nov 2, 2018
Contributor
|
Review app https://hge-ci-pull-917.herokuapp.com is deleted |
Contributor
|
Review app available at: https://hge-ci-pull-917.herokuapp.com |
hasura-bot
pushed a commit
that referenced
this pull request
Aug 1, 2024
<!-- The PR description should answer 2 important questions: --> ### What Change an error down to an issue / warning to unbreak builds. <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> <!-- Does this PR introduce new validation that might break old builds? --> <!-- Consider: do we need to put new checks behind a flag? --> ### How Introduce `BooleanExpressionIssue`, move error value to it, emit this instead. Later we'll turn this into an error based on compatibility date. <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: f0903cc04ea1cf328c9bf67a38d76fd670743679
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.
Description
What component does this PR affect?
Requires changes from other components? If yes, please mark the components:
Related Issue
close #250
Solution and Design
Updated API to create insert permission with insertable
columns.Example on the table
articlewithuserrole :-columnscan bestring( only"*") to specify all columns ({ "columns": "*"}).columnsfield is optional and defaults to*.Type
Checklist: