There have been a few requests in the past for generating multiple time-based UUIDs for the same timestamp but with disparate values (see: , ). I'm creating a new issue as I think we should revisit the idea or at the very least provide some documentation on how to approach this situation.
I think we should consider, one or multiple of the following:
Create documentation for guiding the user through the situation where they want to create multiple rows for the same timeuuid (i.e. creating another column as part of the private key that is a random UUID or something else).
Provide utility method UUIDs.timedBasedRandomLSB with disclaimer that this is not within TimeUUID specification, or provide a way to utilize the microseconds/100 nanoseconds part of the timeuuid
Clarified in the documentation that we don't advocate timestamp-based generation, and added code sample of the workaround if people still want to do it.