|
|
|
|
|
|
by j-pb
1459 days ago
|
|
|
I've had some pretty good experiences with using the following random UID scheme. 32 bit millisecond timestamp that just rolls over, i.e. truncate(current_time_ms()), concatenated with 96 bytes of crypto grade entropy. You get both nice properties, database index locality + proper entropy that you can sleep well and not worry about collisions (since the entire timestamp space will get more densely populated with every overflow (roughly every 50 days)). It's also what PostgreSQL uses for it's index friendly UID format. :D |
|
|