Queries selecting too much data

A query like this:

{
  allTimeobjects (first:1) {
   edges {
    node {
      id,
      beginning,
      end,
      elapsed
    }
  }
  }
}

Executes the exact same SQL as this:

{
  allTimeobjects {
   edges {
    node {
      id,
      beginning,
      end,
      elapsed
    }
  }
  }
}

They also both select all columns and not only the ones we are asking for. (only tested on sqlite but assume postgresql would be the same behavior)

#402 related

[jkimbo]

@OskarPersson @wolendranh I don’t like the idea of building into graphene-django something that always automatically selects only fields that are requested because I think it could actually lead to worse behaviour since Django can’t cache queries consistently. However I would recommend using something like graphene-django-optimiser on a case by case basis if it helps you.

Separately I think #250 is a very good idea and when I get time I’ll look into implementing it.

Going to close this issue now in favour of tracking everything in #250

[wolendranh]

@OskarPersson I get your point. But maybe something like https://github.com/tfoxy/graphene-django-optimizer can be incorporated. Taking into account that related #250