News for hackers. Stuff that matters.
Re:2^120 Ways to Ensure Unique Identifiers by emmab on Wednesday February 11, 2015 @08:36PM (#9036844)
The article would have benefited from explaining in what situations you might prefer this to a UUID
Re:2^120 Ways to Ensure Unique Identifiers by pstrateman on Wednesday February 11, 2015 @08:49PM (#9036891)
The only reason to use this over a UUID is if you want the primary key to be implicitly chronologically ordered.

The ordering guarantee is weak though, it's provided by clients all potentially with their own concept of time.

Re:2^120 Ways to Ensure Unique Identifiers by rosser on Thursday February 12, 2015 @01:58AM (#9037783)
Yeah, you absolutely can't trust client-generated timestamps. We have a table tracking metadata on customer-uploaded photos (dimensions, file size, color profile, &c), including the camera's timestamp. According to their cameras, our customers have uploaded pics taken before the Buddha sat beneath the Bodhi tree, and after the Khitomer Accord was signed.

Fortunately, we also store an upload timestamp, and our servers all sync to local NTP.