[
https://issues.jboss.org/browse/TEIID-4854?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4854:
---------------------------------------
There are 3 resolutions here:
1. document that insert/update/delete is not allowed for non-string values when the
spreadsheet is in a non-english locale
2. Require that the user provides the locale as a property to the resource adapter
3. Upgrade to the v4 apis to automatically determine the locale - this is a fairly
substantial undertaking
There is a related issue with date/time values. The spreadsheet also has a timezone value
that is being ignored - all values are treated as essentially timezone free and read in to
the locale timezone of Teiid.
There is another related issue if the user is using custom formats - while we can obtain
the pattern from the metadata, it is not an exact match for Java formatting. So we cannot
reliable perform insert/update/delete if custom formats are used.
Given all the issues and the scope of 3, it seems like the full resolution may need to be
delayed.
Google translator fails to update timestamp value reformatted after
update
--------------------------------------------------------------------------
Key: TEIID-4854
URL:
https://issues.jboss.org/browse/TEIID-4854
Project: Teiid
Issue Type: Bug
Affects Versions: 9.3, 8.12.10.6_3
Reporter: Lucie Fabrikova
Assignee: Steven Hawkins
Fix For: 9.3
Attachments: gs-reformatted-timestamp.log
Cell of type timestamp is reformatted after an update. Data inserted from teiid are in
format "yyyy-mm-dd hh:mm:ss[.fffffffff]", which is reformatted to
"dd/mm/yyyy hh:mm:ss[.fffffffff]". Subsequent update of such row throws
exception "Could not convert source column Source.smalla.timestampvalue to the
expected runtime type timestamp".
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)