You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in the documentation, creation of COMBs in very quick succession will result in the same embedded timestamp. COMBs with the same timestamp are sorted essentially randomly, since the sort algorithm of your RDBMS will start sorting on the other (non-timestamp) bits of the GUID.
This is sufficient for most needs, such as determining a primary key for a database table. If you need more of a guarantee that COMBs generated will always sort precisely in insertion order, please use UtcNoRepeatTimestampProvider, ideally with UnixDateTimeStrategy. You can see an example of this in the tests:
The text was updated successfully, but these errors were encountered: