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
With UUID7 reaching RFC and obsoleting the previous spec for UUIDs, we now have a UUID format that respects datetime and is far more DB-friendly.
Since ULID can be generated from and returns a unique UUID, can we use ULID as a client/user-friendly representation of the UUIDs stored on the DB?
Would it make sense to change the default implementation of from_uuid to leverage UUID7 ? Or create another function from_uuid7 in order to not break backwards compatibility?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
With UUID7 reaching RFC and obsoleting the previous spec for UUIDs, we now have a UUID format that respects datetime and is far more DB-friendly.
Since ULID can be generated from and returns a unique UUID, can we use ULID as a client/user-friendly representation of the UUIDs stored on the DB?
Would it make sense to change the default implementation of
from_uuidto leverage UUID7 ? Or create another functionfrom_uuid7in order to not break backwards compatibility?Beta Was this translation helpful? Give feedback.
All reactions