Commit 9b29be6
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 4a7ad93 commit 9b29be6
1 file changed
Lines changed: 3 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -5843,7 +5843,9 @@ added: REPLACEME | |||
| 5843 | 5843 | Generates a random [RFC 9562][] version 7 UUID. The UUID contains a millisecond | |
| 5844 | 5844 | precision Unix timestamp in the most significant 48 bits, followed by | |
| 5845 | 5845 | cryptographically secure random bits for the remaining fields, making it | |
| 5846 | - suitable for use as a database key with time-based sorting. | ||
| 5846 | + suitable for use as a database key with time-based sorting. The embedded | ||
| 5847 | + timestamp relies on a non-monotonic clock and is not guaranteed to be strictly | ||
| 5848 | + increasing. | ||
| 5847 | 5849 | ||
| 5848 | 5850 | ### `crypto.scrypt(password, salt, keylen[, options], callback)` | |
| 5849 | 5851 | ||
0 commit comments