robojones / iid Goto Github PK

The time is acutally in seconds, not milliseconds.
The 32 bits of the timestamp are written into the second to 33rd most significant bits, affecting the first five bytes in the byte array.

Many databases only support signed integers. When using iid at its current state the IDs will overflow in a few years when stored in a signed integer.
This could be fixed by shifting the timestamp to the right by one bit reducing the random bits from 32 to 31.