4 ms·
That's because now matter how many times we're told to simply trust uuids we will always want to add a timestamp just in case :) Maybe we should just admit tha
by OzzyB 9y ago
That's because now matter how many times we're told to simply trust uuids we will always want to add a timestamp just in case :)
Maybe we should just admit that no amount of poetic hyperbole like "until an alien invasion" will quell our innate fear of having uuid that will collide.
- reitanqild 9y agoI have heard people laugh at the risk of UUID collisions and thought we were safe but heard two years ago that a consulting company I worked with had seen real issues with UUID collisions on a production system.
- treebeard901 9y agoI doubt many people would argue with the math behind modern uuid generation functions. Those of us that have been around for a while know the problem can come from the implementation and the storage for the UUID. For example: Bugs in code that may generate a unique ID once and then use it multiple places. Imaged OS installations that may cause a UUID to be duplicated Spoofing another ID for malicious reasons Accidental database update statement People tend to give UUIDs magical properties but it needs to be treated similar to an unique integer.
- sroussey 9y agoIf you are using uuid generation that uses MAC address and time stamp, then you can have problems with multiple processes generating uuid for the same system. There are other uuid generation algorithms though.