Uploaded image for project: 'Teiid'
  1. Teiid
  2. TEIID-3923

Remove databasetimezone property from odata4 translator

XMLWordPrintable

    • Icon: Quality Risk Quality Risk
    • Resolution: Done
    • Icon: Major Major
    • 8.13, 8.12.5
    • None
    • Misc. Connectors
    • None

      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.

            [TEIID-3923] Remove databasetimezone property from odata4 translator

            Steven Hawkins added a comment -

            Logged the date/time issue as TEIID-3938 to be tracked separately.

            Steven Hawkins added a comment - Logged the date/time issue as TEIID-3938 to be tracked separately.

            Steven Hawkins added a comment -

            Removed the property from the translator.

            Steven Hawkins added a comment - Removed the property from the translator.

            Ramesh Reddy added a comment - - edited

            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

            Ramesh Reddy added a comment - - edited 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

              rhn-engineering-shawkins Steven Hawkins
              rhn-engineering-shawkins Steven Hawkins
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: