Hacker News new | past | comments | ask | show | jobs | submit login

Or you can just store the UUIDs as bytes like the almighty intended.



UUID is 128 bits.

Even for huge tables 64 bits are enough. And for many tables 32 bits is more than enough.


Oh, 32-bits is enough for a lot of tables assuming you have a transactional ID allocator. The whole reason to have a UUID is so you don't have to serialize all your ID allocation. Agreed though that for some lower volume systems, 64-bits is likely enough to make collisions statistically unlikely.


May be I'm spoiled by postgres, but transactional ID allocator sounds like a problem solved in every database. Is there issues somewhere?


Hehe. It very much is a problem solved in every ACID database... as long as you want to serialize all your transactions.




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

Search: