[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (ODATA-275) Clarify that binding parameters for actions and functions cannot be nullable
[ http://tools.oasis-open.org/issues/browse/ODATA-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32678#action_32678 ]
Andrew Eisenberg commented on ODATA-275:
----------------------------------------
I did not see that the proposed restriction was intended only for entity and collection(entity) parameters.
I believe the same issue exists for parameters of these types. manager may be a nullable entity property of employees. A highlyPaid boolean function may be defined on managers. A query might be submitted:
...$filter=manager/highlyPad()
If highlyPaid cannot accept a null value, then the query writer must explicitly work around this.
> 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]