Split excessive precision exception from out of range exception in Decimal128

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Unknown
    • bson-4.14.0
    • Affects Version/s: None
    • Component/s: BSON
    • None
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None

      Currently Decimal128 raises InvalidRange for two distinct conditions: the value given to Decimal128 is out of range, and the value contains too much precision. The second situation should utilize its own exception class (which will be derived from InvalidRange for now for backwards compatibility) so that the situation is clearly communicated to the users.

            Assignee:
            Oleg Pudeyev (Inactive)
            Reporter:
            Oleg Pudeyev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: