@Alberto Perdomo so this includes the

GraphQL

error?

Yes, it should. The client itself will get better error reporting in the next release, to make this easier to debug as well.

@Perry Raskin Are you referring to the parse error below with certain characters? https://prisma.slack.com/archives/C02EAHBAG93/p1635976318050400?thread_ts=1635963513.049200&cid=C02EAHBAG93

yup

No, unfortunately not. That issue is in Prisma Client and not in the proxy itself. We have identified the issue and are working on a fix. I don’t know yet when this will be released exactly, but I will probably know more on Monday. https://prisma.slack.com/archives/C02EAHBAG93/p1636140293066700?thread_ts=1635963513.049200&cid=C02EAHBAG93

thank u so much!

Hello @Perry Raskin, just wanted to follow up and see if you could switch to 3.4.2 and are using the proxy again without issues.

i’m going to give it a try soon, hopefully this weekend. will let you know for sure!