top | item 36817299 (no title) preseinger | 2 years ago it's commonly totally sufficient for IDs to represent a rough sort ordermillisecond precision is great for a lot of use cases discuss order hn newest willis936|2 years ago I didn't say that it wasn't. Hell even ms is too precise for many use cases (usually where date is used instead).What I said was that it's useful to be able to select timestamp precision independently of UUID implementation. One size that fits all fits none best. dtech|2 years ago Lucky for you, they also define UUIDv8 as a free-for-all where you can do whatever you want, and nanosecond precision is one of the examples given in the RFC.
willis936|2 years ago I didn't say that it wasn't. Hell even ms is too precise for many use cases (usually where date is used instead).What I said was that it's useful to be able to select timestamp precision independently of UUID implementation. One size that fits all fits none best. dtech|2 years ago Lucky for you, they also define UUIDv8 as a free-for-all where you can do whatever you want, and nanosecond precision is one of the examples given in the RFC.
dtech|2 years ago Lucky for you, they also define UUIDv8 as a free-for-all where you can do whatever you want, and nanosecond precision is one of the examples given in the RFC.
willis936|2 years ago
What I said was that it's useful to be able to select timestamp precision independently of UUID implementation. One size that fits all fits none best.
dtech|2 years ago