jdoyle112
09/17/2018, 3:50 PMHenry
09/17/2018, 5:09 PM$delegate
is broken, how are we supposed to load relations in queries now?colburn
09/17/2018, 5:09 PMcolburn
09/17/2018, 5:09 PMHenry
09/17/2018, 5:09 PMHenry
09/17/2018, 5:10 PMcolburn
09/17/2018, 5:11 PMDan Thareja
09/17/2018, 5:12 PMJidé
09/17/2018, 5:12 PMdennisko
09/17/2018, 6:58 PMcode: 3016 message: "Project not found: 'default$default'"
after deploying to DOdennisko
09/17/2018, 6:58 PM/
dennisko
09/17/2018, 6:59 PMlistProjects
returns 1 project as "prisma, staging"dennisko
09/17/2018, 7:00 PMdennisko
09/17/2018, 7:02 PMprisma deploy - Deploying service prisma to stage staging to server default
jreeeee
09/17/2018, 9:18 PMCHaBou
09/17/2018, 9:35 PMstatus
field value is compatible. How can I ensure that? The only way I found is to use updateMany
(even to update a single entity) with a constraint on status
value. It works great but batch updates don't trigger subscriptions 😞marcaaron
09/17/2018, 9:43 PMAndres Montoya
09/17/2018, 11:54 PMcondef5
09/18/2018, 3:37 PMcondef5
09/18/2018, 3:37 PMcondef5
09/18/2018, 3:41 PMcorey.clark
09/18/2018, 6:38 PMXiaoyun Yang
09/19/2018, 1:41 AMprisma.posts()
command will omit the author: User!
field since it's a relation. Do I have to write my own fragment or another graphql query to send via prisma.request
? This seems a little redudant, and I want to use what prisma
has already generated.go4cas
09/19/2018, 5:12 AMgbr-422777
09/19/2018, 8:05 AMJulien Goux
09/19/2018, 8:12 AMJulien Goux
09/19/2018, 8:12 AMJulien Goux
09/19/2018, 8:13 AMJulien Goux
09/19/2018, 8:13 AMJulien Goux
09/19/2018, 8:14 AM