3 ms·
> This is especially important when you use sequential auto-incrementing identifiers with type integer or bigint since they are guessable. I thought we had lon
by SkyMarshal 3y ago
> This is especially important when you use sequential auto-incrementing identifiers with type integer or bigint since they are guessable.
I thought we had long since moved past that to GUIDs or UUIDs for primary keys. Then if you still need some kind of sequential numbering that has meaning in relation to the other fields, make a separate column for that.
- sgarland 3y agoExcept now people are coming back around, because they’re realizing (as the article mentions) that UUID PKs come with enormous performance costs. In fairness, any non-k-sortable ID will suffer the same fate, but UUIDs are the most common of the bunch.