Open
Conversation
Member
|
Hi @rcoup, thanks for your contribution. This is not a use case that we've ever come across and we were curious to hear what you were hoping to achieve with this function. The way we use ULIDs is as opaque identifiers and we've never expected to be able to retrieve the timestamp portion from an existing ULID. Look forward to hearing from you. |
Author
|
Used it for tracing & debugging: grabbing chunks of records associated with a time range or figuring out when a record appeared, in situations where for whatever reason there aren't associated timestamp fields. Most of the language ULID implementations (Python, Go, etc) seem to have parse methods. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Extracts the timestamp from a generated ULID
eg: