[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (ODATA-155) Allow functions to take properties as parameters when used in system query options
[ http://tools.oasis-open.org/issues/browse/ODATA-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31513#action_31513 ] Michael Pizzo commented on ODATA-155: ------------------------------------- Note that the inability to provide properties as function parameters was a bug in the ABNF of the contributed spec; the proposed resolution was the originally intended behavior. > Allow functions to take properties as parameters when used in system query options > ---------------------------------------------------------------------------------- > > Key: ODATA-155 > URL: http://tools.oasis-open.org/issues/browse/ODATA-155 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData ABNF Construction Rules v1.0, OData URL Conventions v1.0 > Affects Versions: WD01 > Environment: [Proposed] > Reporter: Ralf Handl > Fix For: WD01 > > > Functions can be used in e.g. $filter expressions, and currently can only take literal values as parameters. It would be desirable to allow properties as parameters: > GET ~/SalesOrders?$filter=PhoneticallySimilar(Word1='Meier',Word2=Customer/LastName) -- 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]