Define supported numeric promotions

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • V4.0_WD01
    • Affects Version/s: V4.0_WD01
    • Component/s: Protocol
    • None
    • Environment:

      [Proposed]

    • Hide

      Define the following numeric promotions for function parameters and comparisons within filter expressions:

      § If either operand is Edm.Double, the other operand is converted to type Edm.Double.
      § Otherwise, if either operand is Edm.Single, the other operand is converted to type Edm.Single.
      § Otherwise, if either operand is of type Edm.Decimal, the other operand is converted to Edm.Decimal.
      § Otherwise, if either operand is Edm.Int64, the other operand is converted to type Edm.Int64.
      § Otherwise, if either operand is Edm.Int32, the other operand is converted to type Edm.Int32
      § Otherwise, if either operand is Edm.Int16, the other operand is converted to type Edm.Int16.
      § If binary numeric promotion is supported, a service SHOULD use the same semantics as a castExpression to promote an operand to the target type.
      § There's no implicit conversion between string and numeric types.

      Accepted: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/47764/latest/odata-meeting-19_on-20121220-minutes.html

      Show
      Define the following numeric promotions for function parameters and comparisons within filter expressions: § If either operand is Edm.Double, the other operand is converted to type Edm.Double. § Otherwise, if either operand is Edm.Single, the other operand is converted to type Edm.Single. § Otherwise, if either operand is of type Edm.Decimal, the other operand is converted to Edm.Decimal. § Otherwise, if either operand is Edm.Int64, the other operand is converted to type Edm.Int64. § Otherwise, if either operand is Edm.Int32, the other operand is converted to type Edm.Int32 § Otherwise, if either operand is Edm.Int16, the other operand is converted to type Edm.Int16. § If binary numeric promotion is supported, a service SHOULD use the same semantics as a castExpression to promote an operand to the target type. § There's no implicit conversion between string and numeric types. Accepted: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/47764/latest/odata-meeting-19_on-20121220-minutes.html
    • Show
      Accepted: https://www.oasis-open.org/committees/download.php/49026/odata-meeting-34_on-20130425_26-F2F-minutes.html#odata-111

      OData should define the numeric promotions that a service is expected to support; i.e., decimal/double promotions, etc.

            Assignee:
            Unassigned
            Reporter:
            Michael Pizzo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: