Uploaded image for project: 'C# Driver'
  1. C# Driver
  2. CSHARP-2930

Change default GuidRepresentationMode to V3 and default GuidRepresentation to Unspecified

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.0.0
    • Affects Version/s: None
    • Component/s: Serialization
    • None
    • Needed
    • Hide
      1. What would you like to communicate to the user about this feature?
        2. Would you like the user to see examples of the syntax and/or executable code and its output?
        3. Which versions of the driver/connector does this apply to?

      We will need to meet to discuss the broad scope of this change.

      We might need some investigation into suggested migration paths for users.

      Show
      What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to? We will need to meet to discuss the broad scope of this change. We might need some investigation into suggested migration paths for users.

      In version 3.0.0 of the driver we plan to change the default GuidRepresentationMode to V3.

      We should also change the GUID serializer default behavior to handle GUIDs as GuidRepresentation.Unspecified according to the spec thus requiring users to choose whether to use legacy subtype 3 or new standard subtype 4 GUIDs.

      At that time we can also rip out all code that is only for V2 mode.

      We also need to address GUIDs configuration in ObjectSerializer. Open questions are:
      1. Should it fallback to the configured GuidSerializer for GUIDs .
      2. Should we provide more convenient overloads to configure the GUID mode.

            Assignee:
            robert@mongodb.com Robert Stam
            Reporter:
            robert@mongodb.com Robert Stam
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: