You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A very common use case we have in our Dynamo Table are ULIDs used as sort keys: not only does this make it trivial to get the most recent items, but it can also very easily be used to query items by arbitrary date ranges. Except this now requires a Lambda to compute a ULID at the specific timestamp(s) we need in our query,1 to compute the key condition expression.
Would it be reasonable to extend $util.autoUlid2 to accept a timestamp parameter, or alternatively add another built-in function to compute such ULIDs?
A very common use case we have in our Dynamo Table are ULIDs used as sort keys: not only does this make it trivial to get the most recent items, but it can also very easily be used to query items by arbitrary date ranges. Except this now requires a Lambda to compute a ULID at the specific timestamp(s) we need in our query,1 to compute the key condition expression.
Would it be reasonable to extend
$util.autoUlid
2 to accept a timestamp parameter, or alternatively add another built-in function to compute such ULIDs?Footnotes
https://github.com/ulid/javascript?tab=readme-ov-file#seed-time ↩
https://docs.aws.amazon.com/appsync/latest/devguide/built-in-util-js.html#utility-helpers-in-id-gen-js ↩
The text was updated successfully, but these errors were encountered: