Jan Piotrowski

I just tried to reproduce this: ``` C:\Users\Jan\Documents\throwaway>mkdir 17558 C:\Users\Jan\Documents\throwaway>cd 17558 C:\Users\Jan\Documents\throwaway\17558>npm install prisma @prisma/client && npx prisma init && code . added 4 packages, and audited 5 packages in...

I could reproduce with your repository @notmyfiles. Let's see if we can figure out what is going on. Update: I can not reproduce when I run exactly the same commands...

I could isolate the difference of your and my project, it is literally only the encoding of the file: Somehow that is throwing us off. But I have a reproduction...

Ahh, creating the diff via VSCode is a good idea. Let me do that. I used cmd externally via Windows Terminal. Update: Yep, that's it.

Based on the excellent information that @notmyfiles provided, here is a reproduction repository that shows both a working and a non-working migration file: https://github.com/janpio/prisma-repro-17558 The cause seems to be when...

We just released [version 5.12.1](https://github.com/prisma/prisma/releases/tag/5.12.1) which includes a new option `--output` for `migrate diff`. It takes a file path, where the result of your `migrate diff` command output is written...

@manika-khare Can you please share the definition of the (or a reproduction example) stored procedure so we can play with this ourselves? Does the query work when you execute it...

Not a bug we care about too much right now as Azure CosmosDB is not one of our officially supported databases. Just shows again that The MongoDB API of CosmosDB...

No, unfortunately Azure CosmosDB for MongoDB does not support `$$REMOVE` - but Prisma uses `$$REMOVE` to run the queries it needs. As long as that is the state, there is...

The only thing that could help is a reliable reproduction that we can run ourselves that let's us experience the problem ourselves.