Mike Martin

@schickling I'm really excited to see this land in Prisma2. I'd love to see a system that can listen to both scalar updates and relation updates See here: https://github.com/prisma/prisma/issues/146 Also...

@utkarshgupta137 @haifeng-jin This issue is absolutely not solved in the latest version. I'm still getting this on 1.0.8. Can you please re-open this issue?

@jisho-iemoto okay, no problem

Here's a minimal reproduction for the issue. code: ``` import autokeras as ak import numpy as np x = input_node = ak.Input() x = ak.RNNBlock()(x) x = ak.TemporalReduction()(x) output_node =...

@BricePissard Can you update the conflicts? I have a repo where I've fixed the README conflicts if you want to use that. I can't update your branch for you and...

Echoing what @PascalSenn said, but updating `orderBy` to take an array. Arrays have implicit positioning. Objects aren't guaranteed that. Additionally, every related ordering statement must also take an array, so...

@sorenbs If you're switching `orderBy` from `FooOrderByInput` to `[FooOrderByInput!]`, wouldn't that be a breaking change anyway? I've noticed there's some magic in my generator that turns `create: [FooCreateWithoutBarInput!]` into `create?:...

Hi, since we're already talking about a similar issue on another thread, maybe I can chime in here with a suggestion: ``` updateCat( where: {id: "..."}, data: { age_increment: 1...

I agree that by default, disconnects should be idempotent. It's not technically a failure if it was already disconnected. Similar situation to the one above: ``` # datamodel type User...

@mavilein Is Prisma using AMQP 0.9.1 or 1.0? 1.0 will work with Apache ActiveMQ and Amazon MQ, which would make my life much easier. 0.9.1 would require me to spin...