[OASIS Issue Tracker] (ODATA-901) substring: Define negative index for substring function

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

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

Michael Pizzo updated ODATA-901:
--------------------------------

    Proposal: 
In ODATA-781 we defined that a negative index in substring is explicitly undefined, since we did not define a behavior and there were at least two valid interpretations, and that interoperable clients should not use negative indexes. 

In 4.01, we agreed that negative indexes should mean count from the end.

in particular, substring(string,-n,m) is equivalent to substring(string,length(string)-n,m)

  was:
In ODATA-781 we defined that a negative index in substring is explicitly undefined, since we did not define a behavior and there were at least two valid interpretations, and that interoperable clients should not use negative indexes. 

In 4.01, we agreed that negative indexes should mean count from the end.


> substring: Define negative index for substring function
> -------------------------------------------------------
>
>                 Key: ODATA-901
>                 URL: https://issues.oasis-open.org/browse/ODATA-901
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData URL Conventions
>    Affects Versions: V4.0_ERRATA02
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>             Fix For: V4.01_WD01
>
>
> This could be a "bad request" returning no results at all, or it could evaluate to null, which may just lead to excluding the offending instance from the result.
> Or a mix of both: negative start index is "bad request", start index or desired length beyond the end of the first argument is "null".



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)