timestamps returned by the lib lose microsecond precision #494
Labels
api: spanner
Issues related to the googleapis/nodejs-spanner API.
priority: p2
Moderately-important priority. Fix may not be included in next release.
🚨
This issue needs some love.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Hi,
When querying values from Spanner with the nodejs lib, all timestamps lose microsecond precision (they are truncated to milliseconds).
This makes pagination really painful on fields with commit timestamps, since truncating can create lots of cases where entries are missed/duplicate depending on the order.
Other languages (I tried python) properly keep microsecond precision.
Is this a know issue ?
@google-cloud/spanner
version: 2.0The text was updated successfully, but these errors were encountered: