Hacker News new | ask | show | jobs
by AprilArcus 272 days ago
Those seem like standard needs for any kind of CRUD app, so I would call this approach pretty useful. Currently I do something similar by keeping a private primary uuidv7 key with a btree index (a sortable index), and a separate public uuidv4 with a hash index (a lookup index), which is a workable but annoying arrangement. This solution achieves the same effect and is simpler.
1 comments

Why can't you leak timestamp data? What timestamp data is sensitive to your system?

Also, why use UUIDs in that case?