graphql-python / graphql-python/graphene-sqlalchemy

Question: Is over fetching problem solved?

Offen
#109 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Python
Sterne
985
Forks
223
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

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?

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.