graphql-python / graphql-python/graphene-sqlalchemy

Question: Is over fetching problem solved?

未关闭
#109 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Python
星标
985
派生
223
PR 合并指标
30 天内没有已合并 PR

描述

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?

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。