-
Notifications
You must be signed in to change notification settings - Fork 871
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
count(<field>) function broken for empty SELECTs #8621
Comments
Hi @mmacfadden Thank you for reporting, I'm working to a fix now Thanks Luigi |
Hi @mmacfadden I just pushed a fix, it will be released with v 3.0.11 Thanks Luigi |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OrientDB Version: 3.0.9
This is similar to #8280, which seems to only partially have been solved. When using
count(*)
and there are no matching items a proper result set is returned with a count of 0. However if you usecount(<field>)
and there are no matching elements an empty result set is returned.So it seems like
count(*)
works properly.count(<field>)
works when results match, but not when there are not records that match the SELECT.The text was updated successfully, but these errors were encountered: