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
The UUID module documentation mentions that Tarantool generates
UUIDs following the rules for RFC 4122,version 4, variant 1. It is
worth mentioning that the user can store an arbitrary 128-bit sequence
as an UUID for binary data. String representations still should match
the grammars in RFC 4122, Section 3, and RFC 9562, Section 4.
Uh oh!
There was an error while loading. Please reload this page.
Related dev. issue(s): tarantool/tarantool#5444
Related doc. issue: #4333
Product: Tarantool
Since: 3.2
Root document:
SME: @ Buristan
Details
The UUID module documentation mentions that Tarantool generates
UUIDs following the rules for RFC 4122,version 4, variant 1. It is
worth mentioning that the user can store an arbitrary 128-bit sequence
as an UUID for binary data. String representations still should match
the grammars in RFC 4122, Section 3, and RFC 9562, Section 4.
Requested by @ Buristan in tarantool/tarantool@b0b32bf.
The text was updated successfully, but these errors were encountered: