add trailing microsecond 0s to serialized timestamps #301
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
IFC-1374
the new Timestamp using
wheneverstrips trailing zeros from serialized instances. This can cause our database-level datetime comparison logic to break b/c we use string comparison on timestamp fields and a later timestamp with no trailing 0s can appear as earlier incorrectlysmall cypher example
╒════════════════════════════════════════════════════════╕
│"2025-03-12T16:33:54.7Z" > "2025-03-12T16:33:54.710000Z"│
╞════════════════════════════════════════════════════════╡
│true │
└────────────────────────────────────────────────────────┘