How does a mutation like createUser in schema know...
# orm-helpj
Jeff
05/05/2019, 6:45 PMHow does a mutation like createUser in schema know to associate itself with the model User? We don't specifically define the relationship between createUser and User. I could rename createUser to createMember and it'll still work, but how?
n
nuno
05/06/2019, 9:58 AMIn the resolver for
createMemberj
Jeff
05/06/2019, 1:28 PM@nuno sorry I should've been clearer. Take the following code for example,
async createUser(parent, args, { prisma }, info) {
if (args.data.password.length < 😎 {
throw new Error('Password must be 8 characters or longer.')
}
const password = await bcrypt.hash(args.data.password, 10)
const user = await prisma.mutation.createUser({
data: {
...args.data,
password
}
})
return {
user,
token: jwt.sign({ userId: user.id }, 'thisisasecret')
}
}
Jeff
05/06/2019, 1:30 PMThere is no instantiation like in MongoDB where we use new User({ user: req.userId}). It seems like prisma.mutation.createUser() is somehow automatically associating createUser() with User and creating a table named User in Postgres. I've never had to explicitly establish a relationship between createUser and User in graphql. How is this done?
n
nuno
05/06/2019, 2:21 PMThat's handled by the Prisma server. The mutation
createUserUserprismanuno
05/06/2019, 2:24 PMMaybe this could help you: https://www.prisma.io/docs/understand-prisma/prisma-basics-datamodel-client-and-server-fgz4/
nuno
05/06/2019, 2:27 PMAlso, you're using Prisma bindings (https://github.com/prisma/prisma-binding) which doesn't have much documentation now, as they're pushing people to use Prisma Client. Take a look at https://www.prisma.io/docs/faq/prisma-client-vs-prisma-bindings-fq06/
j
Jeff
05/06/2019, 3:24 PM@nuno Thank you for these references. They're extremely helpful 👍
2 Views