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
order by with multiple aggregate fields throws error #2981
Labels
c/server
Related to server
e/quickfix
can be wrapped up in few hours
k/bug
Something isn't working
p/high
candidate for being included in the upcoming sprint
Comments
@ardsh What is the SQL error? |
This is with a slightly different query I executed
|
0x777
added
k/bug
Something isn't working
p/high
candidate for being included in the upcoming sprint
labels
Oct 2, 2019
rakeshkky
added a commit
to rakeshkky/graphql-engine
that referenced
this issue
Oct 3, 2019
@ardsh Thanks for reporting the bug. Please find the fix in #2998. |
That seems to be working well, thank you! |
lexi-lambda
pushed a commit
that referenced
this issue
Oct 5, 2019
polRk
pushed a commit
to polRk/graphql-engine
that referenced
this issue
Feb 12, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
c/server
Related to server
e/quickfix
can be wrapped up in few hours
k/bug
Something isn't working
p/high
candidate for being included in the upcoming sprint
Making a query with 2 aggregate fields in order_by that use min/max and different relations causes an SQL error.
The text was updated successfully, but these errors were encountered: