Luca Steeb
Luca Steeb
Yes, jsonProtocol is currently not supported in the Go client, and it should not be a big deal to implement. Just haven't gotten to it yet
@matt852 Please correct me if I'm wrong, but it looks like you are pointing to Go client issues which are completely unrelated to this repo as it is using the...
Thanks to all for fixing this!
I can also [confirm](https://github.com/prisma/prisma-client-go/runs/2107661585) that the issue is not solved yet, most likely due to the second invocation of tar. @SVilgelm Can we please re-open this issue? Thanks.
sure, ideally it is solved with the `errors` package and then checking for `errors.Is(...)`
Good to know :D though I'm not using this anymore 😅
I'm deploying a NextJS app on CF pages with D1 and I'm running into the same issue (locally, haven't tested in prod). Running this in RSC seems to just produce...
@janpio You are right, I might have confused this one with another and posted a comment. Anyway I have created a new issue https://github.com/prisma/prisma/issues/23929 which also links to the reproduction...
This would be awesome to have, the setup-node action also supports this 👍 > ``` > - uses: actions/setup-node@v3 > with: > # ... > # File containing the version...
Ah yeah, what you mean is https://github.com/steebchen/prisma-client-go/issues/455 and https://github.com/prisma/prisma/issues/10564 So probably some internal command execution (of the JS client) is what is not working. In this case it's not the...