[OASIS Issue Tracker] Updated: (ODATA-15) precision for functions that have Edm.DateTime or Edm.DateTimeOffset parameters

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/ODATA-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-15:
----------------------------

    Proposal: 
Use maximum precision for parameters
Add optional parameter Precision to comparison function, use maximum precision of arguments if not supplied

  was:Use maximum precision for parameters, add optional parameter Precision to comparison function


> precision for functions that have Edm.DateTime or Edm.DateTimeOffset parameters
> -------------------------------------------------------------------------------
>
>                 Key: ODATA-15
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-15
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL v1.0
>    Affects Versions: WD01
>            Reporter: Andrew Eisenberg
>            Assignee: Ralf Handl
>            Priority: Minor
>             Fix For: WD01
>
>
> It is unclear what value of precision should be used for functions that have Edm.DateTime or Edm.DateTimeOffset parameters. Some databases support precisions as high as 12 digits.
> I might like to define a vocabulary with a current_datetime function. What value of precision should be specified for the return type of the function, remembering that the function should be usable across multiple implementations? The same issue arises if I would like to define a compare_datetime function. What value of precision should I use for the two function parameters.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira