fix: date cursor precision string format #1462
Merged
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.
Sql databases (pg/mysql) timestamp precision is 6 subseconds digits max
2024-01-09T22:03:07.195000Z
, which is also a default.Using 3 subseconds digits precision for cursor date->string conversion will not match
2024-01-09T22:03:07.195Z != 2024-01-09T22:03:07.195000Z
on database level which may result in shifted/incorrect pagination for some cases.