[teiid-issues] [JBoss JIRA] (TEIID-5063) Issues with bigdecimal values and odata

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-5063.
-----------------------------------
    Resolution: Done


Updated the visitor logic, changed to just trim trailing 0's, and corrected the odata translator for emitting literals/parameters.  Olingo even with a null precision needs a value for scale as it assumes 0 otherwise, which could be a bug on their part.

> Issues with bigdecimal values and odata
> ---------------------------------------
>
>                 Key: TEIID-5063
>                 URL: https://issues.jboss.org/browse/TEIID-5063
>             Project: Teiid
>          Issue Type: Bug
>          Components: OData
>    Affects Versions: 9.1, 8.12.x-6.4
>            Reporter: Andrej Šmigala
>            Assignee: Steven Hawkins
>            Priority: Blocker
>             Fix For: 10.0, 8.12.x-6.4, 9.3.4, 9.2.6
>
>
> Usage of bigdecimal literals in odata4 translator literals or procedure parameters results in an exception about the facet not being satisfied.
> We are also with TEIID-4269 we were allowing more than just trailing 0s to be trimmed from the numeric values.  This results in situations where you could return an entity with a value, but could not look it up by that value (as it would no longer be equal).  We should instead let the facet fail if we can't just trim zeros.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)