Bram
12/31/2018, 3:38 PMCCBCodeMonkey
12/31/2018, 6:04 PMprisma deploy
supposed to run prisma generate
? because it doesn't seem to for me, seems nice if it wouldroberto.guerra
12/31/2018, 6:04 PMCCBCodeMonkey
12/31/2018, 6:05 PMgraphql get-schema -p prisma
but doesn't actually generate the .graphql file.. I have to run the command separatelyCCBCodeMonkey
12/31/2018, 6:05 PMCCBCodeMonkey
12/31/2018, 6:06 PMEliezer Braun
12/31/2018, 8:58 PMbooting
for a long time.
Then the status is: Not reachable
Any ideas why?
Is there any error logs, helpful messages?
Is this meant to be complicated?CCBCodeMonkey
12/31/2018, 11:20 PMdb.updateUser({
where {
userid:'123'
}
data: {
posts: {
create: {
name:'my new post'
}
},
actions: {
create:{
actionType: 'posted',
post: {
// somehow connect the above created post?
}
}
}
}
});
Mitchell
01/01/2019, 6:08 PMPrisma deploy
step fails. This isn't obvious from the tutorial or the error message. https://www.howtographql.com/graphql-js/4-adding-a-database/Artur Malak
01/01/2019, 6:55 PMArtur Malak
01/01/2019, 7:06 PMRuslan Baigunussov
01/01/2019, 7:18 PMIndustrial
01/01/2019, 9:18 PMIndustrial
01/01/2019, 9:18 PMCCBCodeMonkey
01/02/2019, 3:57 AMZhao
01/02/2019, 4:25 AMupdateMany
. We use it to wrap deletions from two tables into one transaction, we also want to delete the relation between them. We are soft deleting so what we do is actually update
TableA, updateMany
TableB, and disconnect
TableB. It turns out when we have both disconnect
and updateMany
in the same data
object, the updateMany
will be ignored. It seems there is some internal priorities and the disconnect was executed first? Is it a design choice or is it a bug? Thx!shreyansh-zazz
01/02/2019, 7:54 AMrooneyK
01/02/2019, 9:10 AMPost.firstChars
, which returns the first 10 characters of the title
-field. This requires a fragment to be added on Query.posts
which ensures that the field title
is available. This works great when I am accessing the field through posts
, ut for relations accessing Posts.firstChars
, lets say through query{ users{ id posts{ title } } }
, the fragment is of course not available. Is it possible to add the fragment in some other way, so that the field is always available, no matter the root-resolver?Max Ast
01/02/2019, 12:48 PMfgreinus
01/02/2019, 1:01 PMException in thread "main" org.postgresql.util.PSQLException: ERROR: no schema has been selected to create in.I currently have no idea why.. any idea around here? 🙂
Mitchell
01/02/2019, 6:02 PMsubscription {
newLink {
node {
...
}
}
}
Seems this should be:
subscription {
newLink {
...
}
}
https://www.howtographql.com/graphql-js/7-subscriptions/Artur Malak
01/02/2019, 9:08 PMBardhi
01/02/2019, 10:16 PMprismagraphql/prisma:1.19
docker image. I cannot find the source Dockerfile however and don’t want to reverse-engineer/rely on implementation details that might changeserum
01/02/2019, 11:39 PMfindBlasWithFooTextContaining: (_, { search }, ctx) => {
return ctx.prisma
.foos({
where: {
text_contains: search
}
})
.bla()
.then((foos) => {
return R.map(R.prop('bla'), foos);
});
}
so the trick basically was to just shave off the unneeded Foo
😉Eivind
01/03/2019, 8:13 AMAndrew Meyer
01/03/2019, 8:29 AMAndrew Meyer
01/03/2019, 8:50 AMMarvin Jude
01/03/2019, 11:40 AMMarvin Jude
01/03/2019, 11:41 AMStef
01/03/2019, 12:20 PM