[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-1002) Add build in functions operating on collections of primitive (and complex?) types
[ https://issues.oasis-open.org/browse/ODATA-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=65574#comment-65574 ] Michael Pizzo commented on ODATA-1002: -------------------------------------- Should we overload the "in" operator to allow the loperand to be single value or collection, or should we define a new "intersects" operator for this? > Add build in functions operating on collections of primitive (and complex?) types > --------------------------------------------------------------------------------- > > Key: ODATA-1002 > URL: https://issues.oasis-open.org/browse/ODATA-1002 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: New Feature > Components: ABNF Construction Rules, Protocol, URL Conventions > Affects Versions: V4.0_ERRATA03 > Reporter: Hubert Heijkers > Assignee: Hubert Heijkers > Labels: Proposed > Fix For: V4.01_CSD02 > > > I'm getting more asks for people wanting to filter against properties representing a collection of primitive type, most notably Collection(Edm.String). > Things like equal to, not equal to and containing a value or subset are the operations that people are looking to do the most. The size of the array they can get around by using /$count. > Short of coming up with something ourselves I was wondering if this is a more generic ask and if we could maybe guide implementations as to how to support this kind of functionality in a more generic way. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]