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
IQueryable Select statements #5
Comments
Navigation properties are selectively included. for non-navigation properties you can explicitly select what properties to include
Ideally in the future the non-navigation properties would also be selectively included based on the requested fields on the incoming graph |
super nice for navigation properties (AddNavigationField) |
because this
needs to be dynamically constructed. have a look here for the type of code that needs to be written https://github.com/SimonCropp/GraphQL.EntityFramework/blob/master/GraphQL.EntityFramework/Where/ExpressionBuilder.cs |
@SimonCropp i have a navigationField on Customer :
And i still see all the Address fields in the sql query, although i only want Id in the request query |
@flieks happy to accept a PR that fixes that |
@SimonCropp It's possible for Scalar to know which fields to Select on the DBSet so we are interested in implementing this. What do you suggest? |
do you currently have that use case? if not i would ignore it for now |
@SimonCropp yes we have that for many use cases ;). For example a simple one: More thoughts: |
Yep i think its possible |
Interesting, i will check it in a week when i have some time |
Will close this for now. Happy to reopen if someone want to work on it |
Hi @SimonCropp Are select (projections) implemented already ? Will query
execute as
without all other fields in data table ? Regards. |
@sebitsi yes but not as defined in the description above |
@SimonCropp Thanks for your response. What do you mean by
Can you please explain more or point me to documentation. If yes, how it works and what i have to do ? Regards. |
@sebitsi you can read about defining graphs here https://github.com/SimonCropp/GraphQL.EntityFramework/blob/master/doco/defining-graphs.md and there is a runnable sample here https://github.com/SimonCropp/GraphQL.EntityFramework/tree/master/src/SampleWeb BTW if you intending on using the project you should note that it is required that you become a backer https://github.com/SimonCropp/GraphQL.EntityFramework#community-backed |
Hi @SimonCropp.
This config returns data, but there is n + 1 query generated in sql.
Is there an error in my configuration or library cannot handle it.
|
sorry. in the form you want it is not supported. no there is no current plan to add that |
I'm sorry to hear that, This library has potential. Thanks for your time. |
Hi Simon,
Does it only select the fields from IQueryable like Dapper ? Dapper seems alot of coding for each resolver so it would be nice not to have to implement Dapper.
The text was updated successfully, but these errors were encountered: