OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (ODATA-1041) Broaden definitions of transformations topcount and bottomcount


Gerald Krause created ODATA-1041:
------------------------------------

             Summary: Broaden definitions of transformations topcount and bottomcount
                 Key: ODATA-1041
                 URL: https://issues.oasis-open.org/browse/ODATA-1041
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: New Feature
          Components: OData Extension for Data Aggregation
    Affects Versions: V4.0_CSD03
         Environment: Proposed
            Reporter: Gerald Krause
             Fix For: V4.0_CSD04


Definitions in section 3.2 and 3.6 state that the second parameter must result in a primitive numeric value. This is too restrictive, actually it is only required that there is a total ordering on these values.

Consider, for example, getting the latest stock by product: $apply=groupby((Product),topcount(1,Date))




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