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.

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

GraphQL does not support EXISTS #1655

Closed
elprans opened this issue Aug 11, 2020 · 0 comments · Fixed by #1672
Closed

GraphQL does not support EXISTS #1655

elprans opened this issue Aug 11, 2020 · 0 comments · Fixed by #1672
Assignees
Labels
Projects

Comments

@elprans
Copy link
Member

elprans commented Aug 11, 2020

There seems to be no way to test for empty set in GraphQL filters.

@elprans elprans added this to To do (release: Aug 24th) in Alpha 5 via automation Aug 11, 2020
@vpetrovykh vpetrovykh moved this from To do (release: Aug 24th) to In progress in Alpha 5 Aug 13, 2020
vpetrovykh added a commit that referenced this issue Aug 18, 2020
The `exists` filter operation appears at every nested level regardless
of whether the level represents a link or a property. The operation
takes either a `true` or `false`, which translates to `EXISTS` and `NOT
EXISTS` EdgeQL respectively.

Update the GraphQL documentation and cheat sheet.

Fixes #1655
Alpha 5 automation moved this from In progress to Done Aug 19, 2020
vpetrovykh added a commit that referenced this issue Aug 19, 2020
The `exists` filter operation appears at every nested level regardless
of whether the level represents a link or a property. The operation
takes either a `true` or `false`, which translates to `EXISTS` and `NOT
EXISTS` EdgeQL respectively.

Update the GraphQL documentation and cheat sheet.

Fixes #1655
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Alpha 5
  
Done
Development

Successfully merging a pull request may close this issue.

2 participants