Serhii Tatarintsev

No worries, @paulomarg, thank you for submitting the PR anyway. It won't be able to be merged is more of our failure than yours, to be honest, so, my apologies...

@davecarlson I was not the one who closed the PR, but if you look at updated snapshots here, it is pretty far even from a baseline — `generate` message you...

Hey, the issue looks like a mistmatch between `@prisma/client` and `prisma` packages or missing `prisma generate` after the update. Does it still happen to anybody on prisma 5+?

Hey @smg-helenyemima , With the lack of information and our inability to reproduce this issue, we're now closing it. Feel free to comment if you have any updates about it....

This is generally true for non-extended `$connect` too - executing request will establish the connection to the database, but it will not do so by calling the same public `$connect`...

Unfortunately, we need way more than wire protocol compatibility to support a database. ClickHouse with MySQL-like network interface is very far from an actual MySQL instance and is not supported...

Sorry, can not provide ETA at the moment. Query extensions seem to have a problem with Fluent API in general and we probably should fix it in Prisma Client rather...

Aforementioned PR got merged and released, there is a logging example in README now: https://github.com/prisma/extension-read-replicas#pre-configured-clients

Hey everyone, Sehii from Prisma team here. We would really like to support Nitro and Nuxt edge deployments and I did my own short investigation into the problem. You can...

@pi0 thanks for the fix! I've updated by reproduction to the latest unwasm version. Now we are getting different error: ```ts [unwasm] Failed to parse WASM module wasm/query_engine_bg-5343c5664d9b411c.wasm: Error: [unwasm]...