Skip to content
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

OData support for $select #284

Open
mgroves opened this issue Apr 9, 2020 · 1 comment
Open

OData support for $select #284

mgroves opened this issue Apr 9, 2020 · 1 comment

Comments

@mgroves
Copy link
Contributor

mgroves commented Apr 9, 2020

A question came in from Stack Overflow on OData with Linq2Couchbase: https://stackoverflow.com/questions/61078681/how-to-apply-odata-select-after-couchbase-iqueryable-is-executed

A minimum source code to reproduce the issue is here: https://github.com/ofthelit/ODataCouchbase

It looks like $select causes a NotImplementedException. I ran the code, and found that the N1QL itself is generated correctly and executes correctly. But in BucketQueryExecutor.cs, ExecuteCollection, running the query results in the exception. Supporting a $select seems like a common scenario in OData. Is this a bug, or is this just not yet supported? What would it take to get it supported?

(See also issue #222)

@brantburnett
Copy link
Collaborator

@mgroves Frankly, my hope is that an EF Core 3 provider will address most of the problems. When I looked into it previously, the OData lambdas were especially complicated. I believe that EF Core would handle most of that complexity for us, without reinventing the wheel.

That said, it's possible that some of the simpler cases like select might be supportable. We'd have to see.

Also, the problem might be this: #134 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants