[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-827) introduce $compute query option
[ https://issues.oasis-open.org/browse/ODATA-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61352#comment-61352 ] Mark Stafford commented on ODATA-827: ------------------------------------- My intention with the last URL was to force us to consider an example that doesn't use $compute but uses the computed property in two other QSPs. The ordering of evaluation is an interesting point, but my intention here was to focus on flexible URLs. I don't like the price mul quantity syntax as much as price*quantity but I can imagine that things like division would create a bit of a headache with URL parsing. > introduce $compute query option > ------------------------------- > > Key: ODATA-827 > URL: https://issues.oasis-open.org/browse/ODATA-827 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData Protocol, OData URL Conventions > Affects Versions: V4.0_WD01 > Environment: New Query Capabilities > Reporter: Andrew Eisenberg > Labels: GoodIdea, Usability > Fix For: V4.01_WD01 > > > OData could be extended to allow derived computed values to be returned along with the properties of an entity. > This could be expressed as: > http://odata.netflix.com/v2/Catalog/Titles?$compute=substring(ShortSynopsis,20) as Summary&$select=Name,Summary > In ODATA-9 we added support for an equivalent compute transformation in our Data Aggregation Extensions. -- 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]