[teiid-issues] [JBoss JIRA] (TEIID-3923) Remove databasetimezone property from odata4 translator

Ramesh Reddy (JIRA) issues at jboss.org
Fri Jan 22 10:12:00 EST 2016


    [ https://issues.jboss.org/browse/TEIID-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152513#comment-13152513 ] 

Ramesh Reddy edited comment on TEIID-3923 at 1/22/16 10:11 AM:
---------------------------------------------------------------

Steve:

After looking at the source though, I'm not so sure about this. 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. This seems like it could be a bug since it is asymmetric behavior. I can't find any spec reference on this either.

Van:
I agree, this is a good candidate for 8.12.x.

Ramesh:
I have posted a question to the Olingo development group here http://markmail.org/search/list:org.apache.olingo.dev#query:list%3Aorg.apache.olingo.dev+page:1+mid:bfghfslrpwyjh6ii+state:results


was (Author: rareddy):
Steve:

After looking at the source though, I'm not so sure about this. 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. This seems like it could be a bug since it is asymmetric behavior. I can't find any spec reference on this either.

Ramesh:
I have posted a question to the Olingo development group here http://markmail.org/search/list:org.apache.olingo.dev#query:list%3Aorg.apache.olingo.dev+page:1+mid:bfghfslrpwyjh6ii+state:results

> Remove databasetimezone property from odata4 translator
> -------------------------------------------------------
>
>                 Key: TEIID-3923
>                 URL: https://issues.jboss.org/browse/TEIID-3923
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: Misc. Connectors
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 8.13
>
>
> The databasetimezone execution property is not used - and not needed since all date/time information needs to be in gmt or with an explicit timezone.
> This is a candidate for 8.12.5 as well.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the teiid-issues mailing list