[
https://issues.jboss.org/browse/TEIIDDES-1810?page=com.atlassian.jira.plu...
]
Dan Florian commented on TEIIDDES-1810:
---------------------------------------
No [~blafond]. The real value is the one that will be stored in the EObject property (so
it will have the precision loss). The displayed value, coming from the EMF annotation
property is strictly for the user to give them a warm and fuzzy feeling that the number
they entered is _exactly_ the number we are using. Again, with numbers this large, the
difference in the numbers is relatively extremely small and the user will not know the
difference.
All values in the PropertiesView are shown as Strings [~mmakovy] regardless of their real
type. The problem is that when we roundtrip the new value (obtaining the new long value,
conversion from long to int, converting to String for PropertiesView) the value has
changed. What I am proposing in #2 is that we save that original long value as an
annotation. Then when displaying in the PropertiesView we would first look for that
annotation, and if it exists, we would use that as the value instead of the actual value
found in the object's property.
Support larger statistic values
-------------------------------
Key: TEIIDDES-1810
URL:
https://issues.jboss.org/browse/TEIIDDES-1810
Project: Teiid Designer
Issue Type: Enhancement
Components: Patch Release, Teiid Integration
Reporter: Steven Hawkins
Assignee: Dan Florian
Fix For: 10.0.1, 9.2.1
The table/column stats are currently limited to max int (2^31 -1) values.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)