[
https://jira.jboss.org/jira/browse/TEIID-7?page=com.atlassian.jira.plugin...
]
Ramesh Reddy updated TEIID-7:
-----------------------------
Component/s: Query Engine
Fix Version/s: 6.1.0
Affects Version/s: 6.x
Affects: [Compatibility/Configuration, Release Notes] (was: [Release Notes,
Compatibility/Configuration])
Control of BigDecimal precision and scale
-----------------------------------------
Key: TEIID-7
URL:
https://jira.jboss.org/jira/browse/TEIID-7
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.x
Reporter: Jerry Helbling
Priority: Minor
Fix For: 6.1.0
Problem 1: The parser defaults to parsing literals that look like bigdecimal as doubles,
which have no scale.
Workaround (which is on devcentral): You can avoid the above conversions by wrapping the
values in a convert in the query (example: "convert('123.00', BigDecimal
)").
A better fix is update the parser to look for loss of scale information and to use the
bigdecimal type instead.
Problem 2: default division behavior JBEDSP-305
Problem 3: No explicit control via the parser
It would be good to provide explicit precision and scale via "convert(xxx,
BigDecimal(10, 2))" - side note bigdecimal is a bad name for this type. it should
really just be decimal
Reference: This is related to Issue Tracker Issue 175485.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira