[teiid-issues] [JBoss JIRA] (TEIID-4269) numeric calculated fields not displayed with odata4

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493934#comment-13493934 ] 

Steven Hawkins commented on TEIID-4269:
---------------------------------------

[~jstastny] TEIID-5063 limited the scope of these changes to just trim trailing zeros (which are considered non-significant in sql for comparison purposes) - otherwise there will be issues with searching.  This also satisfies this issue as logged, but as you are seeing will fail for situations where the calculation doesn't fully match the expectations.  We can add a doc note about using round or perhaps it would be better to include a different exception message indicating round should be used.

> numeric calculated fields not displayed with odata4
> ---------------------------------------------------
>
>                 Key: TEIID-4269
>                 URL: https://issues.jboss.org/browse/TEIID-4269
>             Project: Teiid
>          Issue Type: Bug
>          Components: OData
>    Affects Versions: 8.12
>            Reporter: Mirco Marchitiello
>            Assignee: Ramesh Reddy
>             Fix For: 9.1, 8.12.x-6.4
>
>
> I've created a virtual table with a new field defined in this way:
> select ROUND((BA.PREIS / BA.PEINH), 3) AS UnitPrice from xxxxxx
> for the source field are bigdecimal I define UnitPrice as
> BigDecimal (13,3)
> If I run the qery from JDBC
> select * from PurchaseRequisitionEntity where PurchaseRequisitionKey = '300-8000001452-00010' ;
> PREIS = 539,568
> PEINH = 106
> UnitPrice = 5,090.264
> And the result is correct. If I run from odata2
> /odata/CASALE.1/Entities.PurchaseRequisitionEntity('300-8000001452-00010')?$format=json
> "UnitPrice" : "5090.2640000000000000"
> As you can see the field is rounded to the 3rd digit but 13 more digits are returned with 0 value.
> Anyway odata2 succeeds in returning the result without errors.
> With odata4 I get an error:
> /odata4/CASALE.1/Entities/PurchaseRequisitionEntity('300-8000001452-00010')?$format=json
> {"error":{"code":null,"message":"The value '5090.2640000000000000' is not valid for property 'UnitPrice'."}}
> I think that's because the length of the field is greater then the matedata definition.
> At the moment the only solution I can imagine is to convert the number to a string in the proper format and the parse it into a number



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)