[
https://issues.jboss.org/browse/TEIID-3938?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3938:
-------------------------------------
Unfortunately there is no such agreement to keep the values in/out in GMT in OData
specification, it just that these values do not have any TZ info at all. Treating them
strings or some special construct in Java would have been straight forward, since they are
ties to java.sql.Time and java.sql.Date it is making difficult. The right (talking it
loosely, I am lost what is right..) thing to do is, define another property such as
"defaultTimeZoneForEdmDate" and have a default to "GMT". That way it
can be configurable, and decision is in the hands of the developer. For unit tests I can
lock it with GMT. WDYT?
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)