I've started using ULIDs when I need IDs that are time-sortable while still reta... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		jdcarter on June 9, 2017 \| parent \| context \| favorite \| on: Be Careful with UUID or GUID as Primary Keys I've started using ULIDs when I need IDs that are time-sortable while still retaining the advantages of a UUID. Read more here: `https://github.com/alizain/ulid` The ultra-quick summary: 48 bits of timestamp followed by 80 bits of randomness. Also, when representing as strings, they use Crockford Base32 encoding, meaning 26 characters instead of a UUID's 36. (I'd argue that UUIDs should use this encoding as well.)

Scirra_Tom on June 10, 2017 [–]

I would think it would be better to keep the time stamp in a separate column. In essence you're duplicating the time stamp across FKs which is space wasteful - and a little abstract as one field is holding multiple data.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact