New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for $compute in $select and $filter #799

Closed
ysanghi opened this Issue Apr 28, 2017 · 0 comments

Comments

Projects
None yet
3 participants
@ysanghi
Contributor

ysanghi commented Apr 28, 2017

Short summary (3-5 sentences) describing the issue.
OData 4.01 adds a new "$compute" clause for computing expressions that can then appear in $select, and in results as dynamic columns.

See http://docs.oasis-open.org/odata/odata/v4.01/csprd01/part2-url-conventions/odata-v4.01-csprd01-part2-url-conventions.html#_Toc470093702.

We need this functionality so that we can issue requests like:
http://host/api/Collections(‘id’)/Items?$select=Property1,Property2
&$compute=Cast(Prop1,’Edm.Int32) as Property1, Cast(Prop2,’Edm.String’) as Property2

Assemblies affected

OData.NET 7.X

Reproduce steps

Trying $compute with ODataUriParser doesn't parse the query parameter as a valid supported query parameter as detailed in the spec.

Expected result

What would happen if there wasn't a bug.
We can parse the URI segments and also write computed values in the response for both typed and untyped values.

Actual result

What is actually happening.
The query parameter is just ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment