[OASIS Issue Tracker] Commented: (ODATA-275) Clarify that binding parameters for actions and functions cannot be nullable

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

    [ http://tools.oasis-open.org/issues/browse/ODATA-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32665#action_32665 ] 

Andrew Eisenberg commented on ODATA-275:
----------------------------------------

I am envisioning an XML exists function that is something like:

http://.../employees$filter=resume/XML.exists(query="... $it ...")

I am planning to allow the bound parameter to be nullable, and to have the function return false for each resume that is null.

If XML.exists was not nullable, then what would the query do for null resumes? I cannot find a statement in our specs to cover this. Error? Automatically return null?



> Clarify that binding parameters for actions and functions cannot be nullable
> ----------------------------------------------------------------------------
>
>                 Key: ODATA-275
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-275
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData CSDL
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_WD01
>
>
> Bindable actions and functions take an entity or collection of entities as their first parameter. We did not explicitly state that this binding parameter must not be nullable, but it's rather hard to imagine a use case for applying a bindable function or action to "nothing".

-- 
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