[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-1499) Clarify how to allow/dissalow unbound functions in $filter/$orderby
Christof Sprenger created ODATA-1499: ---------------------------------------- Summary: Clarify how to allow/dissalow unbound functions in $filter/$orderby Key: ODATA-1499 URL: https://issues.oasis-open.org/browse/ODATA-1499 Project: OASIS Open Data Protocol (OData) TC Issue Type: Improvement Components: Protocol Affects Versions: V4.01_ERRATA01 Reporter: Christof Sprenger [11.5.4.1 Invoking a Function|https://docs.oasis-open.org/odata/odata/v4.01/os/part1-protocol/odata-v4.01-os-part1-protocol.html#sec_InvokingaFunction] states (emphasize mine) {quote}Functions can be used within $filter or $orderby system query options. Such functions can be bound to a resource, as described above, *or called directly* by specifying the namespace- (or alias-) qualified function name. {quote} It states how bound functions can be used. The standard also explains how function imports can be used but there seems to be now explanation if and how they are connected for the "called directly" case. What is necessary to use a function in $filter an $apply? (e.g. is a function import necessary?) And depending on the answer, how can it's usage in these cases be restricted/disabled ? -- This message was sent by Atlassian Jira (v8.3.3#803004)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]