graphql-python / graphql-python/graphene-sqlalchemy

Question: Is over fetching problem solved?

Open
#109 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
985
Forks
223
PR merge metrics
No merged PRs in 30d

Description

I am transitioning to python from C#, I know in C# the problem of over fetching data has not yet been solved. But in javascript it has been solved by [Join Monster](https://github.com/stems/join-monster).

I have been looking at the issues here, and I see that there is a couple instances of recommendations on how to use lazy loaders to solve the N+1 problem. But I haven't seen any on how to solve the over fetching issue.

Is there a supported solution for over fetching currently or am I on my own piecing it together from other sources?

A second question is if Dataloaders is now the recommended method of solving the N+1 problem or are lazy loaders the recommended method?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.