Serhii Tatarintsev

Panic is never expected, this issue is about having a proper error instead.

Latest commit adds a simple crate for encoding the schema. Usage: ``` cargo run -p compile-schema ``` With that utility, we can compare the impact of bincode on the schema...

Quickly tried `postcard` instead of `bincode`. Without reproducing the whole table, sizes are similar to bincode with variable encoding: For odooo schema we are at 227 968 bytes uncompressed and...

I think this is consistent with pretty much any doc-comment systems out there? Putting empty line after a comment would detach it from the thing it used to document in...

Hi @piotrkulpinski. Does the issue reproduce with an empty Turso database, or only when there is specific data in it? If later, could you provide a sample of that data?

Hi @langleyd This is a bug on Nitro's side. There is unfortunately no workaround we can do on our side. We've already reported it [here](https://github.com/unjs/nitro/issues/2242), you can follow the progress...

Michael is right [here](https://github.com/hayes/pothos/issues/1190#issuecomment-2062637680), we've removed a property from edge build to save on the bundle size, since most of our users don't use `Prisma.dmmf`. Edge builds with driver adapters...

Also, please make sure you are using `prisma://` url as your connection string - extension alone is not enough to get accelerate working.

Hi @dengfuping Could you fill an issue template and specify how to reproduce the issue in terms of prisma behavior? I am not sure what the screenshots of our code...

@serg06 ~we are a little bit behind on docs with that, but~ as of latest Prisma version it is possible to implement that universally with `$allModels` and a couple of...