A bug in conversion of milliseconds
A bug in conversion of milliseconds

Rethink stores time as a floating point number with precision to milliseconds. Go's native time has precision to nanoseconds. The gorethink's conversion of time from float64 milliseconds to time.Time creates artifacts in microseconds and nanoseconds. With the current code every time.Time fetched from RethinkDB it must be rounded to milliseconds if consistency of stored vs retrieved value is important. It makes sense to do correct rounding in the driver. The fix ensures that the time is consistent.
brendanobrienesq/gorethink,SKatiyar/gorethink,dancannon/gorethink,dancannon/gorethink,GoRethink/gorethink,dancannon/gorethink,GoRethink/gorethink,GoRethink/gorethink