Title
h
Haider Malik
07/18/2018, 7:48 AMschema.graphqltype User {
id: ID! @unique
email: String!
password: String!
role: Role @default(value: "CANDIDATE")
}prisma.graphqltype Query{
user(where: UserWhereUniqueInput!): User
}
input UserWhereUniqueInput {
id: ID
}UserWhereUniqueInputasync function login(root, { email, password }, ctx, info) {
const user = await ctx.db.query.user({ where: { email: email } }, ` { id password } `)
....
}{
"data": null,
"errors": [
{
"message": "Variable \"$_v0_where\" got invalid value {\"email\":\"<mailto:Jane2@email.com|Jane2@email.com>\"}; Field \"email\" is not defined by type UserWhereUniqueInput.",
"locations": [],
"path": []
}
]
}a
Arnab
07/18/2018, 8:06 AMI'm guessing (could be wrong) that it's because
emailuniqueUserWhereUniqueInput👍 2
In other words, if you want to be able to do this query, then you need the
email: String! @uniqueh
Haider Malik
07/18/2018, 8:08 AMLet me try it. I resolved this issue by using this logic
const [user] = await ctx.db.query.users({ where: { email: email } },)a
Arnab
07/18/2018, 8:09 AMYes, using the
usersuserh
Haider Malik
07/18/2018, 8:09 AMErrors:
User
✖ You are making a field unique, but there are already nodes that would violate that constraint.type User {
id: ID! @unique
email: String! @unique
password: String!
role: Role @default(value: "CANDIDATE")
}a
Arnab
07/18/2018, 8:10 AMYes, I'm guessing multiple users have the same email.
h
Haider Malik
07/18/2018, 8:10 AMLet me delete the data from my prisma service
a
Arnab
07/18/2018, 8:10 AMBut wait. What do you actually want to do? Do you want your user objects to have unique emails?
Or do you want them to be able to have non-unique emails and be able to search amongst them?
h
Haider Malik
07/18/2018, 8:11 AMYeah, Each user must have unique email
a
Arnab
07/18/2018, 8:11 AMThen you can enforce that first
h
Haider Malik
07/18/2018, 8:14 AMawesome! It is working now
Thanks
a
Arnab
07/18/2018, 8:14 AMGlad to help 🙂