Does `prisma.user(…)` do any caching? I'm starting...
# orm-helpr
rem
01/21/2019, 6:21 PMDoes
prisma.user(…)Userprisma.user(…).<relation>/Types/User.jsh
Harshit
01/21/2019, 6:22 PMWe batch everything using dataloader
Harshit
01/21/2019, 6:22 PMso your final thing will result in single hit to the database
Harshit
01/21/2019, 6:23 PMmeans user(...).<relation> will be converted in such a SQL statement in prisma server that it will grab all things at once
r
rem
01/21/2019, 6:32 PMperfect 👍
rem
01/21/2019, 6:43 PMIs it right that I'm having to manually define each relation in my types/User.js file? I thought that if I didn't define the type property, then Prisma would pick up the property.
Because until I manually added the User.accountSubscription resolver, running a query for that field in the playground would return null (or an error saying it can't be null).
h
Harshit
01/21/2019, 6:49 PMIt is fine to use that pattern to resolve them 🙂
r
rem
01/21/2019, 7:01 PMbut, if I don't explicitly include them, the values don't resolve at all. Is that right?
h
Harshit
01/21/2019, 7:02 PMYes, that ensures safety and will make sure you don't forget to resolve a field.
Harshit
01/21/2019, 7:04 PMhttps://github.com/javascript-af/javascript-af/blob/master/packages/backend/src/resolvers/User/User.ts
I also do the same with my projects. If you use TS, graphqlgen will automate this
r
rem
01/21/2019, 7:07 PM…this project has definitely got me more interested in TS…!