Retrieve fields on mapped Django models efficiently about graphene HOT 5 CLOSED

I've written something along these lines for my own project. It just works on a connection at the moment. It uses the info to work out which fields (if any) are being requested on the underlying node, and then checks the corresponding node type for a optimize_foo classmethod. If that exists, it passes the queryset through that method, before passing the queryset to the connection_from_foo function. They have a similar signature to a resolver. You have to be careful in resolver methods that both optimized and non-optimized cases are covered in some cases.

class PostNode(DjangoNode):
    [...]

    @classmethod
    def optimize_owner(cls, queryset):
        return queryset.select_related('owner')

    @classmethod
    @with_context
    def optimize_loved(cls, queryset, context):
        # Sets user_loves attribute on post
        return queryset.prefetch_user_loves(context.user)

    @with_context
    def resolve_loved(self, args, context, info):
        try:
            return self.user_loves
        except AttributeError:
            return self.love_set.filter(user=context.user).exists()

    @classmethod
    def optimize_field_with_arguments(cls, queryset, args):
        return queryset.process_args(args)

from graphene.

I think you can get this info from the query AST, but there should be a more convenient way to get this.

from graphene.

Related issue needed to resolve before this task: #57

from graphene.

@syrusakbary I think this issue can be closed? If it's still an issue then it should be raised on the graphene-django repo

from graphene.

Yup, we can close the issue here and reopen in graphene-django if necessary

from graphene.