Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on SCRU128: Sortable, Clock and Random number-based Unique identifier. Parent comment
You can do both, use a low precision timestamp with overflows in the ID to keep the index happy, and add a proper timestamp field for analytics.
The 32 + 96 split is what postgres uses for example. I'd say that's a pretty good endorsement.
There are no comments on this comment yet.
You can do both, use a low precision timestamp with overflows in the ID to keep the index happy, and add a proper timestamp field for analytics.
The 32 + 96 split is what postgres uses for example. I'd say that's a pretty good endorsement.