-
Notifications
You must be signed in to change notification settings - Fork 37
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
Comparison to null in Filter expression #203
Comments
I've written some unit tests in a branch, PR #204. Oddly, I can't get the behavior that you see where you get back an empty enumerable. I created three test cases with two variations:
I've only had errors where the code won't work at all. None of them worked but caused no results to return. Would you mind taking a look at my tests and see if they represent the situation you're running into? |
I'm not sure what Nancy is doing, but just throwing back the Many thanks for looking at this so quickly, sorry for sending you on a wild goose chase. |
Great; the |
I believe this issue is fixed in the issue_203 branch. If you have the time, could you take a look and verify before I merge that branch? :-) |
Many thanks Mathieu. I just tested your changes and they work for me. I can see the fix is not quite obvious, but I'm getting a better idea of how this library and rethinkdb communicate. |
Thanks for the issue report, and the other PRs you submitted. I love having new contributors to this project. :-) Let me know if there's anything I can do to help you understand and participate in the project more. |
At first I thought rethinkdb-net didn't support
Nullable<DateTime>
inside aFilter()
expression, so I tried bothx == null
andx.HasValue
, both didn't work, then I tried with a string and that also didn't work. Following is the ReQL query and the C# I'm trying to use, I just get back an empty enumerable without anything matching:ReQL:
C#:
I had a look through the source code to work out how I'd fix this, but I'm quite lost and I suspect this fix is going to be quite involved. Any chance you've got some time to fix it or point me in the right direction? Thanks.
The text was updated successfully, but these errors were encountered: