Object with uninitialized DateTime throws error about rethinkdb.driver HOT 4 CLOSED

Hi @fiLLLip

I think this is the expected behavior w.r.t RethinkDB. According to the technical details:

https://www.rethinkdb.com/docs/dates-and-times/java/#technical-details

The docs mentions a Max/Min Year range [1400, 10000] for DateTime. .NET supports DateTime ranges from 1/1/0001 12:00:00 AM (uninitialized) to 12/31/9999 11:59:59 PM. So, an uninitialized date falls out of this range.

Perhaps, you could model an uninitialized DateTime as a nullable?

from rethinkdb.driver.

I see 👍 I will change the type to DateTime? in my models 😄

from rethinkdb.driver.

@fiLLLip , I think I found a bug in DateTime? nullable while writing a large object storage extension to the driver. Just want to give you a heads-up. This will be fixed in a next point release. The bug is: Nullable date / time defined as DateTime? or DateTimeOffset? get serialized as json strings in iso8601 format (Newtonsoft's DateTime string), not as ReQL pesudo types. So, if you look at two dates DateTime and DateTime? in the same document in data explorer, you'll notice one is native and the other is a datetime string.

from rethinkdb.driver.

Thanks for the heads-up! I haven't tested DateTime at all before this, so I wouldn't notice the difference I think 👍

from rethinkdb.driver.