Julius de Bruijn
Julius de Bruijn
Yup. It is quite bad.
Close. Yeah, we try to parse integers as `i64`, that will overflow with big values. I'm between is this a bug or an improvement, but also considered it to be...
A reproduction was done in https://github.com/prisma/prisma/issues/14632#issuecomment-1243415138 so moving this to the repair team!
I cannot reproduce this. I started with two clean databases: `database_a` and `database_b`. Created a new Prisma project explicitly with version 4.2.0 used in this issue. ``` root@51a758d136a2:~/test/test-project# npx prisma...
Wait a week more or so for the next otlp crates to come out and this one gets a bit easier. https://github.com/open-telemetry/opentelemetry-rust/pull/1674
Yup, you are right, we closed the wrong issue. The correct one is https://github.com/prisma/prisma/issues/7293 Sorry about that, switching the issues and reopening this.
Is there a way to get this docker image working with TLS on Catalina? I've heard problems with Azure SQL too, where the certificate is not accepted by Apple...
The problem is how JavaScript's Date is by default represented as UTC. When Prisma only uses `DateTime` underneath, what happens here is the stringified date we get from the client...
Could somebody tell me what is needed to get this one merged? I could try to finish it up, but I'm not sure why the current PR is not good...