Non-canonical Decimal128 serializes incorrectly

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Go Drivers
    • 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?

      Show
      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?
    • None
    • None
    • None
    • None
    • None
    • None

      Context

      Go Driver's Decimal128 constructor accepts direct bytes that represent the data, but does not canonicalize these values. Some non-canonical representations can cause exceptions in the driver, exceptions that the user may not be expecting.

      Node Driver team is planning on adding validation methods to the next version of the driver, so users will be able to choose to canonicalize their Decimal128 data.

      Definition of done

      Up to you.

      Pitfalls

      Non-canonical Decimal128 data is already out there, we should be careful about how any kind of validation/canonicalization is added.

            Assignee:
            Unassigned
            Reporter:
            Pavel Safronov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: