Skip to content

GraphQL Field Collection for avoid dataloaders and solve N+1 problem differently #1074

Open
@frederikhors

Description

@frederikhors

Hi all! 😃

I'm using gqlgen (like juniper but in Go not in Rust) and Ent as ORM (but is more than an ORM).

I'm writing to you because I just found out an excellent feaure of Ent: GraphQL Field Collection.

Since I found out SeaORM and their amazing summer project I asked them if would be possibile to add this feature on SeaORM too when using it with juniper.

Basically Ent with this feature offers the possibility to AVOID ALL THE DATALOADERs.

Do you think juniper offers the ability to do that?

Can we use some juniper "metadata" to instruct SeaORM (or others) to detect what edges are being requested in queries?

I still don't know juniper, excuse the maybe silly question. I am preparing for my - hopefully very close - switch to Rust.

Thank you for your work.

Activity

tyranron

tyranron commented on Jun 25, 2022

@tyranron
Member

@frederikhors from what I see:

The Ent extension for field collection adds support for automatic GraphQL fields collection for associations (i.e. edges) using eager loading.

May be this crate will help: https://docs.rs/juniper-eager-loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementImprovement of existing features or bugfixsupport

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @tyranron@frederikhors

        Issue actions

          GraphQL Field Collection for avoid dataloaders and solve N+1 problem differently · Issue #1074 · graphql-rust/juniper