-
Notifications
You must be signed in to change notification settings - Fork 22
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
Null and NotNull where conditions not supported #17
Comments
It should be supported– this is a bug. Will take a PR. |
After further research, the not null and null are supported; however, they are only supported for scans, not for index queries. With that in mind, I believe that the indexes are being improperly chosen. For example, if you pass through the primary hash and a non-index based column, it will STILL try to use the primary index which results in error. The solution is to confirm that all columns passed through the where clause are actually apart of an index. If they are not, then a scan should be performed instead. |
Ah, you're probably right. I'm pretty sure that should be detected right around here: Line 708 in 9ca0c93 |
We agree as well. We don't have the time to push a PR right now so we wanted to get all of the info here for anybody else. |
When testing query using where clause with either 'null' or 'notNull' conditions specified, an error occurs.
Code:
Error:
Are these intentionally no longer supported? If so, can we update the documentation, as it can be misleading?
The text was updated successfully, but these errors were encountered: