16 ms·
That's what created_at and updated_at are for surely
by xmdx 3y ago
That's what created_at and updated_at are for surely
- sam_lowry_ 3y agoFrom the ActiveRecord fame ;-)
- yesimahuman 3y agoI was going to ask, when would you only rely on a sequential id for temporal locality, wouldn't most people be indexing and sorting on `created_at` or something equivalent?
- Tehnix 3y agoYou don’t need to need temporal elements, the simple fact that UUIDs are a bad fit for B-Trees means that simply inserting a bunch of data that relies on a UUIDv4 for its unique ID, will also run into these same problems. You’d typically see this as either lower performance of a table than you expect, or higher IOPS usage of your database (which gets expensive at scale).