Graphql - fix pagination bug due to ms precision
When we use keyset pagination inside GraphQL our cursors are missing millisecond data for timestamps, which causes pagination to not work properly when objects have the same timestamp up to the second, as the database sees for example '23:14:56' as '23:14:56.0000' which is different from any other timestamps with millisecond values that are not '0000'
Showing
Please register or sign in to comment