graphql-python / graphql-python/graphene-sqlalchemy

Question: Is over fetching problem solved?

Abierto
#109 3 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Python
Estrellas
985
Forks
223
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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?

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.