Re:Database Design Mistakes
by jasonlotito on Saturday July 20, 2013 @07:58PM
(#6077096)
To be fair, he seemed to be referring to non-sequential GUIDs. And I can understand his point. If the only thing a GUID provides is a unique ID, it's not doing much with all that room it takes up.
[ Parent
| on HN ]
Re:Database Design Mistakes
by merlincorey on Saturday July 20, 2013 @09:02PM
(#6077311)
I didn't even know there were actual sequential GUIDs until I just googled for them. Thanks!
Seems they are mostly just like autoincrement integers with the random GUID data following. I guess you still have the storage constraints, but now you at least can order them easily.
Re:Database Design Mistakes
by jasonlotito on Saturday July 20, 2013 @10:32PM
(#6077539)
Just in the interest of sharing more on IDs, I found this an interesting read:
http://instagram-engineering.tumblr.com/post/10853187575/sha...