[
https://issues.jboss.org/browse/TEIID-3938?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3938:
---------------------------------------
If there is agreement that Edm.Date and Edm.TimeOfDay should default to GMT in/out, then a
property isn't needed unless you are trying to maintain backwards compatibility. I
was thinking when I first looked at the patch that your flag on EdmDateTimeOffset changed
the actual value, but it just selects between equivalent string forms for the same
instant. A flag for Edm.Date and Edm.TimeOfDay would actually change the values.
EdmDate and EdmTimeOfDay output in local timezone
-------------------------------------------------
Key: TEIID-3938
URL:
https://issues.jboss.org/browse/TEIID-3938
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Fix For: 8.12.5
EdmDate and EdmTimeOfDay both assume GMT for incoming string values - however when the
convert from Java objects to string they use the local/default Calendar. So when Teiid is
on a server not in GMT date and time value sent via the odata4 translator will likely be
wrong.
Ramesh:
I have posted a question to the Olingo development group here
http://markmail.org/search/list:org.apache.olingo.dev#query:list%3Aorg.ap...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)