[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-747) Allow IEEE 754 constants [-]INF and NaN also for Edm.Decimal
[ https://issues.oasis-open.org/browse/ODATA-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60664#comment-60664 ] Ralf Handl commented on ODATA-747: ---------------------------------- Protocol Version Negotiation: - If the client doesn't send an odata-maxversion header, or sends one that includes V4.01, it may get these values. - If the client specifies odata-maxversion:4.0 it won't get the new values, instead it will get a 500 Internal Server Error because the service is unable to serialize the backend data. > Allow IEEE 754 constants [-]INF and NaN also for Edm.Decimal > ------------------------------------------------------------ > > Key: ODATA-747 > URL: https://issues.oasis-open.org/browse/ODATA-747 > 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: [Proposed] > Reporter: Gerald Krause > Labels: AdoptionBlocker > Fix For: V4.01_WD01 > > > Just as for IEEE 754 floating-point numbers, calculations of Edm.Decimal values also can lead to results that can only be represented by constants for "Not a Number" or "(negative) Infinity". -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]