Arnab
02/04/2019, 10:07 AMasync addPersonToCoop(parent, args, context) {
return await prisma.updateCoop({
data: {
people: {
connect: {id: args.personId}
}
},
where: {id: args.coopId}
})
}
When I do the query directly to prisma, it works:
mutation{
updateCoop(where: {
id: "cjrmnfndf003x0854f33kk8c6"
},
data: {
people: {
connect: {id: "cjrq5m7qa004g0854lgiggn59"}
}
}
){
name
id
people{
id
name
}
}
}
but when I run the mutation that I wrote myself, it says that it can't return null for a non-null field (the people field)csbdeak
02/04/2019, 10:13 AMcsbdeak
02/04/2019, 10:13 AMezeikel
02/04/2019, 11:34 AMUby
02/04/2019, 11:54 AMnexus
?Uby
02/04/2019, 11:55 AMKen
02/04/2019, 2:21 PMKen
02/04/2019, 2:22 PMJeunesse Burce
02/04/2019, 2:41 PMZyon
02/04/2019, 6:01 PMKenan Pulak
02/05/2019, 1:11 AMpostgres
and db port to 5432
to match postgres defaults. However when Iâm launching the Fargate instance it keeps on failing. I think it is having an issue with the PRISMA_CONFIG
env var because the logs show that itâs having difficulty parsing the string. Does anyone else have experience with this? Or if not, what is the structure of the env vars that Prisma is expecting?Kenan Pulak
02/05/2019, 1:11 AMKenan Pulak
02/05/2019, 1:12 AMbepasquet
02/05/2019, 3:22 AMbepasquet
02/05/2019, 3:22 AMbepasquet
02/05/2019, 3:23 AMArnab
02/05/2019, 12:31 PMasync personConnection(parent, args, context, info) {
return await prisma.personsConnection()
}
However, when I add the properties one by one:
const aggregate = await prisma.personsConnection().aggregate()
...
return { aggregate, pageInfo, edges }
This worksLuc
02/05/2019, 2:44 PMyolen
02/05/2019, 3:16 PMekfn
02/05/2019, 3:32 PMprisma
?csbdeak
02/05/2019, 3:46 PMantonbramsen
02/05/2019, 4:14 PMtonymj
02/05/2019, 6:00 PMtonymj
02/05/2019, 6:02 PMMax Ast
02/05/2019, 6:32 PMDan Ramos
02/05/2019, 6:53 PMCCBCodeMonkey
02/05/2019, 7:16 PMMarcin MikoĹajczak
02/05/2019, 8:39 PMMarcin MikoĹajczak
02/05/2019, 8:39 PMMarcin MikoĹajczak
02/05/2019, 8:40 PM