You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@olingo.apache.org by "Christian Amend (JIRA)" <ji...@apache.org> on 2016/02/12 10:57:18 UTC

[jira] [Resolved] (OLINGO-749) Support Higher precision for TimeStamps

     [ https://issues.apache.org/jira/browse/OLINGO-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Amend resolved OLINGO-749.
------------------------------------
    Resolution: Fixed
      Assignee: Christian Amend

Should be fixed with this commit: https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=d18f9f0bdf915031e31d796250aea30b7fbf9a9b

V2 now supports the Timestamp object for higher precision. 

> Support Higher precision for TimeStamps
> ---------------------------------------
>
>                 Key: OLINGO-749
>                 URL: https://issues.apache.org/jira/browse/OLINGO-749
>             Project: Olingo
>          Issue Type: Improvement
>          Components: odata2-core
>    Affects Versions: V2 2.0.2, V2 2.0.3, V2 2.0.4, V2 2.0.5, V2 2.0.6
>         Environment: OData Provisioning, Consumption
>            Reporter: Sachin
>            Assignee: Christian Amend
>             Fix For: V2 2.0.7, V2 2.1.0
>
>
> Hi,
> Currently in Olingo, a precision of 3 is supported at the most for Edm.Time,DateTime. This limitation needs to be addressed as there are OData V2 services which has values with higher precision. This affects both provisioning and consumption scenarios.
> Thanks,
> Sachin



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)