dohomi
02/07/2018, 7:13 AMthe request could not be satisfied
at the momentJosef Henryson
02/07/2018, 7:20 AMChristian
02/07/2018, 8:27 AMsiyfion
02/07/2018, 11:03 AMsiyfion
02/07/2018, 11:07 AMrafaelcorreiapoli
02/07/2018, 11:08 AMtype Technology {
id: ID! @unique
name: String!
childTechnologies: [Technology!]! @relation(name: "ChildTechnologies")
parentTechnologies: [Technology!]! @relation(name: "ChildTechnologies")
}
When trying to add a child to this technology with
ctx.db.mutation.updateTechnology({
where: {
id: "techA"
},
data: {
childTechnologies: {
connect: {
id: "techB"
}
}
}
}, info)
The final result becomes:
{
"data": {
"technologies": [
{
"id": "techA",
"name": "My Technology Updated",
"childTechnologies": [
{
"id": "techB"
}
],
"parentTechnologies": [
{
"id": "techB"
}
]
},
{
"id": "techB",
"name": "Another Technology",
"childTechnologies": [],
"parentTechnologies": []
}
]
}
}
Where it should be
{
"data": {
"technologies": [
{
"id": "techA",
"name": "My Technology Updated",
"childTechnologies": [
{
"id": "techB"
}
],
"parentTechnologies": []
},
{
"id": "techB",
"name": "Another Technology",
"childTechnologies": [],
"parentTechnologies": [
{
"id": "techA"
}
]
}
]
}
}
Vendicto
02/07/2018, 11:08 AMVendicto
02/07/2018, 11:34 AMpokorson
02/07/2018, 11:50 AMgraphql-yoga
and Prisma, I've used starter project and took subscriptions
example from prisma repo. When tested in playground and db tab subscriptions works fine, but when I added them to my schema I'm not getting any message from server. That's how my mutation resolver look:
sendMessage(parent, { type, message, chatId }, ctx, info) {
return ctx.db.mutation.createMessage(
{
data: {
chat: {
connect: {
id: chatId,
},
},
type,
message,
},
},
info
);
},
pokorson
02/07/2018, 11:50 AMmessage: {
subscribe: async (parent, args, ctx, info) => {
return ctx.db.subscription.message({}, info);
},
},
pokorson
02/07/2018, 11:50 AMpokorson
02/07/2018, 11:55 AMTsupol
02/07/2018, 12:08 PMDavid Darrell
02/07/2018, 12:13 PMYou can verify that the new user is there by sending the users query in the dev Playground in the database project.
would look like.David Darrell
02/07/2018, 12:20 PMdocker exec -it prisma-db mysql -u root --host 127.0.0.1 --port 3306 --password=prisma
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 1045 (28000): Access denied for user 'root'@'127.0.0.1' (using password: YES)
David Darrell
02/07/2018, 12:25 PMgraphcool
docs stated prisma
David Darrell
02/07/2018, 12:28 PMMoritz
02/07/2018, 12:53 PMtype Mother{
id: ID! @unique
children: [Children!]!
}
type Children{
id: ID! @unique
mother: Mother
}
and later change it to
type Mother{
id: ID! @unique
children: [Children!]!
}
type Children{
id: ID! @unique
mother: Mother!
}
making the dependency required, I get the output error:
Hooks:
Checking, if schema file changed !
▸ MotherUpdateWithoutChildrenDataInput fields must
▸ be an object with field names as keys or a
▸ function which returns such an object.
I get this issue even after running prisma delete
and then running prisma deploy
. Does anyone have any Ideas how to interpret this?Vendicto
02/07/2018, 1:29 PM{uri: "file:///path/CoreSimul…ocuments/8C027537-CFE5-47A4-8BFB-CF131DFE56A9.jpg", name: "IMG_0002.JPG", type: "image/jpeg"}
schava
02/07/2018, 1:56 PMschava
02/07/2018, 1:56 PMmplis
02/07/2018, 3:13 PMjuicycleff
02/07/2018, 3:30 PMMoritz
02/07/2018, 3:31 PMreturn ctx.db.mutation.updateBook(
{
where: { id },
data: {
author: {
connect: {
id: authorId
}
}
cover: {
connect: {
id: coverId
}
}
}
}, info)
Wherein authorId
and coverId
could optionally be empty.
If I simple pass the empty parameters i get the You provided an invalid argument for the where selector
error message.matthewdschulman
02/07/2018, 3:46 PMmatthewdschulman
02/07/2018, 3:46 PMKimo
02/07/2018, 3:57 PM{
"data": {
"authenticateUser": null
}
}
rajit
02/07/2018, 3:59 PMmatthewdschulman
02/07/2018, 4:03 PM