[DOCS-1543] UUID BinData subtype Created: 27/May/13  Updated: 30/Oct/23  Resolved: 27/Jul/16

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Minor - P4
Reporter: Adam Comerford Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

All


Issue Links:
Related
related to PHPC-895 Require 16-byte data length for Binar... Closed
related to CSHARP-228 Support standard byte order when seri... Closed
related to JAVA-403 UUIDs are stored as little endian (sh... Closed
related to PYTHON-267 Support Binary subtype 4 for UUID Closed
related to SERVER-12835 UUID() shell method should use binary... Closed
Participants:
Days since reply: 7 years, 29 weeks ago

 Description   

There are 2 UUID subtypes define as part of the BSON spec. Type 3, the legacy one, is deprecated. However it is still the only one really supported by the drivers.

Type 4 was introduced to solve some problems with Type 3 but is not fully implemented yet in the drivers.

We need to document the two different types and explain that while you should use type 4, there is no proper validation of the UUID when inserted as BinData type 4, hence the burden falls to the application to enforce validity.



 Comments   
Comment by Emily Hall [ 27/Jul/16 ]

Closed by Emily Hall for Housekeeping on 7/27/16.
Please create a new ticket if for prioritization.

Thank you!

Comment by Bernie Hackett [ 22/Jan/14 ]

We should document the expected byte format for subtype 4. Languages that don't have a native UUID type but still want to store "uuid" bytes in a BinData have to store the bytes in the format defined by the RFC.

http://docs.python.org/2/library/uuid.html#uuid.UUID.bytes
http://tools.ietf.org/html/rfc4122#section-4.1.2

Comment by Jeremy Mikola [ 22/Jan/14 ]

Should drivers for languages without a native UUID type do anything here? Isn't there still an issue with endianness that we might want to take care of? Binary data with subtype 3 and 4 are have different data in raw BSON, but they should logically have the same value.

Comment by Adam Comerford [ 27/May/13 ]

Linking related driver issues for some history/flavor.

Generated at Thu Feb 08 07:41:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.