[teiid-issues] [JBoss JIRA] (TEIID-5077) Couchbase strange behaviour for long numbers
[
https://issues.jboss.org/browse/TEIID-5077?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5077:
---------------------------------------
If the column in source model is modelled as string, shouldn't
the value be actually retreived as string, without the TONUMBER function?
Only if you are querying the source table directly. If you query the view and it adds a
conversion that is supported by the source, then we'll push it down.
Of course if we feel this is something that we want to compensate completely for, then we
would need to change the import type mapping for long/biginteger to string and remove
support for the pushdown of conversion to long/biginteger.
This also calls into question the support of bigdecimal as the issue implies the only
numeric type that is properly supported is double - but bigdecimal expects fixed and
possibly arbitrary precision.
Couchbase strange behaviour for long numbers
--------------------------------------------
Key: TEIID-5077
URL: https://issues.jboss.org/browse/TEIID-5077
Project: Teiid
Issue Type: Bug
Components: Documentation, Misc. Connectors
Affects Versions: 8.12.x-6.4
Reporter: Jan Stastny
Assignee: Steven Hawkins
Priority: Critical
There is a strange limitation for storing large numbers (e.g. modelled as long) in
Couchbase.
https://forums.couchbase.com/t/strange-behavior-when-saving-big-long-numb...
The same behaviour with value: 28341791043587382
which is being stored and retreived as: 28341791043587384
I feel we need to document this behaviour and provide hints how to overcome it.
(Modelling of the column as string on Couchbase's side and defining a view).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)