[OASIS Issue Tracker] (ODATA-557) Allow exponential notation for Edm.Decimal

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/ODATA-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60909#comment-60909 ] 

Mark Biamonte commented on ODATA-557:
-------------------------------------

What does a scale of floating represent?  Does it mean that the data is a DECFLOAT with an exponential notation string representation for the value?
I assume it is up to the server to determine when to represent the data in exponential notation or not.  Should a preference be provided to the user to allow them to suggest whether a string representation or an exponential notation is used?  For example the result may have some DECFLOAT values that can be represented in the string representation very efficiently and others that have to be represented in exponential notation.  The use might prefer to see all values as exponential notation in this case.

WIth Aggregation, can canonical functions be applied to properties in the $select?  If so another option to a preference is to ad a canonical function that forces the value representation to string or to  exponential notation. 

> Allow exponential notation for Edm.Decimal
> ------------------------------------------
>
>                 Key: ODATA-557
>                 URL: https://issues.oasis-open.org/browse/ODATA-557
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ABNF Construction Rules, OData ATOM Format, OData CSDL, OData JSON Format, OData Protocol, OData URL Conventions
>    Affects Versions: V4.0_CSD03
>         Environment: Decimal
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>              Labels: AdoptionBlocker
>             Fix For: V4.01_WD01
>
>
> IEEE754 also defines the DECFLOAT data type for high-precision decimal arithmetic. They have 16 or 34 decimal digit mantissas and exponents between -383 and +384 or -6143 and +6144.
> Representing them exactly in current Edm.Decimal would result in at most 34 non-zero digits and several thousand zeroes. This waste can easily be avoided by allowing exponential notation also for Edm.Decimal.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)