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

Fixed handling of DateTime.MinValue. Issue #240 #241

Merged
merged 2 commits into from
Nov 22, 2015

Conversation

ThomasHoest
Copy link

Fixed long and ulong MaxValue and MinValue checks

(cherry picked from commit 6d878131fb4b5b8f402bcd5b43c7b0afa2c03d77)
@mfenniak
Copy link
Owner

Sure, that change to the test makes sense; we just can't represent the long values with the same precision as the double. But, it looks like the same test failure you encountered in the long datum converter still exists in the unsigned long datum converter. Could you please fix that up too?

Errors and Failures:

  1. Test Failure : RethinkDb.Test.DatumConverters.UnsignedLongDatumConverterTests.ConvertDatum_ValueTooLargeToRepresentAsLongProperly_ThrowException
    System.NotSupportedException was expected

Other than that, this looks good to merge. If you can push a fix for that and the CI goes green, I'll merge it up.

@ThomasHoest
Copy link
Author

Ups forgot that one. It should be fixed now

mfenniak added a commit that referenced this pull request Nov 22, 2015
Fixed handling of DateTime.MinValue. Issue #240
@mfenniak mfenniak merged commit 335ef0d into mfenniak:master Nov 22, 2015
mfenniak added a commit that referenced this pull request Nov 22, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants