Commit 1684ab8
doc: note non-monotonic clock in crypto.randomUUIDv7
Signed-off-by: nabeel378 <mohammadnabeeljameel@gmail.com>
PR-URL: #62600
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>1 parent 67e0ac5 commit 1684ab8
1 file changed
Lines changed: 3 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -5822,7 +5822,9 @@ added: REPLACEME | |||
| 5822 | 5822 | Generates a random [RFC 9562][] version 7 UUID. The UUID contains a millisecond | |
| 5823 | 5823 | precision Unix timestamp in the most significant 48 bits, followed by | |
| 5824 | 5824 | cryptographically secure random bits for the remaining fields, making it | |
| 5825 | - suitable for use as a database key with time-based sorting. | ||
| 5825 | + suitable for use as a database key with time-based sorting. The embedded | ||
| 5826 | + timestamp relies on a non-monotonic clock and is not guaranteed to be strictly | ||
| 5827 | + increasing. | ||
| 5826 | 5828 | ||
| 5827 | 5829 | ### `crypto.scrypt(password, salt, keylen[, options], callback)` | |
| 5828 | 5830 | ||
0 commit comments