Thiago Bellini Ribeiro

@shmoon-kr oh, I see what you mean You can probably do something similar to what I do on strawberry-graphql-django for `ListConnectionWithTotalCound`: https://github.com/strawberry-graphql/strawberry-graphql-django/blob/main/strawberry_django/relay.py#L51 In there I overridden `resolve_connection` to store `nodes`...

@fireteam99 > would it be possible to prevent or delay the queryset from being evaluated by next_ in a field extension? Yeah, that's the optimizer doing its thing =P The...

> From what I understand, the qs._fetch_all() is used by the internal optimizer? I'm curious why I didn't encounter any n+1 issues even after disabling it. Actually the opposite. `qs._fetch_all()`...

> Oh interesting! Does that mean disabling qs._fetch_all() prevents the query from running async? It prevents you from returning querysets to be resolved at graphql-core level, as iterating over them...

Hey @fireteam99 , I think this should allow you to solve your issue: https://github.com/strawberry-graphql/strawberry-django/pull/481 When it is merged, you just need to do `field.disable_fetch_list_results = True` in your extension `apply`...

> Gotcha gotcha, so this shouldn't be an issue as long as I'm not using async? No. Although strawberry-django will do the fetching for both, unless you set the `disable_fetch_list_results`...