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
Copy file name to clipboardExpand all lines: README.md
+17-4Lines changed: 17 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,12 +7,25 @@
7
7
8
8
UUIDv7 for Elixir and (optionally) Ecto, using an 18-bit randomly-seeded counter.
9
9
10
-
There are other UUID v7 packages, but I wanted the additional precision.
11
-
12
-
Uses suggestions described in **[Section 6.2](https://www.ietf.org/archive/id/draft-ietf-uuidrev-rfc4122bis-14.html#name-monotonicity-and-counters)**
13
-
from [this IETF Draft](https://www.ietf.org/archive/id/draft-ietf-uuidrev-rfc4122bis-14.html)
10
+
Uses suggestions described in **[Section 6.2](https://www.ietf.org/archive/id/draft-ietf-uuidrev-rfc4122bis-14.html#name-monotonicity-and-counters)** from [this IETF Draft](https://www.ietf.org/archive/id/draft-ietf-uuidrev-rfc4122bis-14.html)
14
11
to add additional sort precision to a version 7 UUID.
15
12
13
+
## When should I use this package?
14
+
15
+
- You want sequential, time-based, ordered IDs (per-node).
16
+
- You are willing to trade a small amount of raw performance for these
17
+
guarantees. You are taking a hit for backwards time-leap protection and the
18
+
counter with rollover protection.
19
+
20
+
## When should I not use this package?
21
+
22
+
- You don't care about sort/order precision beyond milliseconds.
23
+
24
+
There are other UUID packages, that only have millisecond precision, for example:
0 commit comments