[
https://issues.apache.org/jira/browse/OLINGO-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298043#comment-15298043
]
Sagar commented on OLINGO-749:
------------------------------
Hi Amend,
Isn't '2016-05-23T11:51:00.8398830Z' is valid format for Edm.DateTimeOffset
field. I believe as per the specification
http://www.odata.org/documentation/odata-version-2-0/overview/ (Chapter # 6.
Primitive Data Types) this is valid format for DateTimeOffset data type.
I will appreciate your comments on this ?
-Sagar
> 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
>
> Attachments: DateTimeOffset.jpg
>
>
> 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)
