Skip to content
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.

Sign up for GitHub

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

Jump to bottom

issue with insert nested object #844

Closed
ilovelll opened this issue Oct 24, 2018 · 0 comments · Fixed by #852
Closed

issue with insert nested object #844

ilovelll opened this issue Oct 24, 2018 · 0 comments · Fixed by #852
Assignees
@rakeshkky
Labels
c/server Related to server e/intermediate can be wrapped up in a week k/bug Something isn't working p/urgent Immediate action required
Milestone
v1.0.0-alpha28

Comments

@ilovelll
Copy link

When I try to follow the docs on "Insert nested object and get nested object in response", i found an issue that,
when I try to do this with "returning" everything works fine,

but when i try to returning with "affecting rows", only the author insert, there's nothing change on the article, even though the returing result was "affecting rows: 2".
@coco98 coco98 added k/bug Something isn't working p/urgent Immediate action required labels Oct 24, 2018
@0x777 0x777 added c/server Related to server e/intermediate can be wrapped up in a week labels Oct 24, 2018
@0x777 0x777 removed their assignment Oct 24, 2018
@0x777 0x777 added this to the v1.0.0-alpha26 milestone Oct 24, 2018
@rakeshkky rakeshkky mentioned this issue Oct 24, 2018
Merged
21 tasks
@0x777 0x777 modified the milestones: v1.0.0-alpha26, v1.0.0-alpha27 Oct 26, 2018
@0x777 0x777 closed this as completed in #852 Nov 2, 2018
0x777 pushed a commit that referenced this issue Nov 2, 2018
@rakeshkky @0x777
refactor nested insert mutation and fix returning (fix #844) (#852)
0e9d699 
* improved nested insert execution logic

* integrate error path, improve executing 'withExp' and improve tests

* add more readable types in '/Resolve/Insert.hs'

* set conflict context just before executing WITH expression
@snyk-bot snyk-bot mentioned this issue Oct 13, 2022
Merged
hasura-bot pushed a commit that referenced this issue Jul 17, 2024
@danieljharvey @hasura-bot
Return BooleanExpressionError from object-boolean-expressions stage (#…
342ff1f 
…844)

<!-- The PR description should answer 2 (maybe 3) important questions:
-->

### What

Much like this change, but for the `object_boolean_expressions` stage:
hasura/v3-engine#843

<!-- What is this PR trying to accomplish (and why, if it's not
obvious)? -->

<!-- Consider: do we need to add a changelog entry? -->

### How

<!-- How is it trying to accomplish it (what are the implementation
steps)? -->

V3_GIT_ORIGIN_REV_ID: 85da185b45bac429b754b0b92419f378a59fb536
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rakeshkky rakeshkky

Labels
c/server Related to server e/intermediate can be wrapped up in a week k/bug Something isn't working p/urgent Immediate action required
Projects
None yet
Milestone
v1.0.0-alpha28
Development

Successfully merging a pull request may close this issue.

refactor nested insert mutation and fix returning (fix #844) rakeshkky/graphql-engine
4 participants
@coco98 @ilovelll @0x777 @rakeshkky