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
Given only 168140 rows, we're seeing 4 UUID generation collisions across the entire set even when when copycat.uuid is fed with unique-to-that-table data. Different inputs are giving the same outputs.
This occurs for us regardless of whether we use our integer IDs or prefixed-cuids as the input.
Thanks for the ticket @djm! We've released 0.6.0, where md5 alone is being used for hashing - this should make the chance of collisions significantly lower.
If you'd like to try this out in snaplet, we've released 0.15.0, which includes the new copycat version with this change.
I know I also promised you more details about collision probabilities with copycat (months ago now!) and haven't gotten back to you yet. Still on my list, and will let you know as soon as I have more details for you!
In the meantime, could you try out the new snaplet / copycat and see how it works for you?
Version 0.5.0
Given only 168140 rows, we're seeing 4 UUID generation collisions across the entire set even when when
copycat.uuid
is fed with unique-to-that-table data. Different inputs are giving the same outputs.This occurs for us regardless of whether we use our integer IDs or prefixed-cuids as the input.
Replication:
Output:
https://replit.com/join/krqpfrimzc-darianmoody
The text was updated successfully, but these errors were encountered: