fix timestamp test
The existing timestamp test checked the values within 50ms of each other, since 50ms was a realistic latency for the existing test framework (locally on travis with pg, mysql, etc). The mssql tests generally take much longer, but this solution accounts for both and future cases.
Showing
with
1 additions
and
1 deletions
-
Please register or sign in to post a comment