[ https://issues.oasis-open.org/browse/ODATA-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61554#comment-61554 ]
Michael Pizzo commented on ODATA-784:
-------------------------------------
All of the implementations follow Evan's proposed rules for add/sub/mult. None of the implementations appear to follow Evan's rule for div.
Most of the Div examples seems to return the value in the max scale of the underlying type.
=>How would a client know this value?
=>If an implementation is aggregating data from multiple underlying sources, how could it return (or even correct for) a single value for max scale? Would it be forced to convert everything to the min max scale?
There seem to be at least 5 proposals for div:
Scale(A)
Scale(A)+Scale(B)
Scale(A)-Scale(B)
>= Scale(A) (doesn't seem to address Evan's second case (A div 3) gt 0.3)
max precision of decimal
Susan will look to see what IEEE 754-2008 (ISO/IEC/IEEE 60559:2011) specifies.
> Need to specify the behaviour of arithmetic operators on Decimal type
> ---------------------------------------------------------------------
>
> Key: ODATA-784
> URL: https://issues.oasis-open.org/browse/ODATA-784
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Improvement
> Components: OData URL Conventions
> Affects Versions: V4.0_OS
> Environment: Proposed
> Reporter: Evan Ireland
> Priority: Minor
> Fix For: V4.01_WD01, V4.0_ERRATA03
>
>
> The rules for scale of results of decimal arithmetic operators are not specified.
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
