Prisma

this is like you want to cache individual nodes of a query at edge

so like `query { foo { name } bar { name } }`

and you want to cache the result for `query { foo { name }` and `query { bar { name } }` separately

and then combine those values if you get foo &amp;&amp; bar

or if you get `query { foo { name } post(1) { title } }` then `foo` comes from the cache

which I think is way more complexity than needed, and you should just wrap your resolver in a caching function

caching the entire query sounds far more reasonable

(although, likely could break with query batching by clients)

I guess one thing that could be done is sending variables by header instead of post body

In it's simplest form you could probably do just `sha1(req.body)` to cache

i see, it sounds pretty complex :slightly_smiling_face: 
Isn’t the graphql dataLoader enough for caching? 
Or is it because it’s better to be able to let people from around the globe hit up different instances of varnish depending on their location ?

(sorry if it’s noobish, I’m getting more and more in to backend development atm)

it's like if you're querying for articles by id, without user-specific data

then it's better to store copies as close as possible to the edge (the user), rather than actually hitting your server and having your server do work

Ah yeah ofc, because even with DataLoader the server still does the work of returning the cache

Thanks for explaining it for me <@U2YPM3EAX>

also, with DataLoader, the loaders are usually only caching per request, not per server

ah, so if i’m firing a request with multiple queries and parts like `author {…}` is the same :open_mouth: 
I actually got the impression that it made a full server cache so the next request would read from a cache. Wow, i’m stoked, i misunderstood big time then

if you create your Dataloader instance on request, then it's per request

i.e., <https://github.com/facebook/dataloader#creating-a-new-dataloader-per-request>

Hi! 
I’m trying to create a change password form, but i can’t figure what mutations i need to change password of a user. 

Looking at the mutation `updateUser` the only arguments are `id, username`. Any help would be useful :slightly_smiling_face:

hey <@U36M03M46> I will have a look right away :simple_smile:

hey <@U2W0V6RFE>, that is not possible at the moment. we just discussed our road map for email/password: <https://github.com/graphcool/feature-requests/issues/39> with things like email validation and reset password emails. would be nice if you could add your thoughts :simple_smile:

Hey everyone <!here|@here>! Even though it has been available for a few days now, today we're officially introducing support for Auth0 &amp; Digits. You can read more about it here: <https://blog.graph.cool/user-authentication-in-graphql-with-auth0-digits-4ce01788950>