Nikolas

> What I used here is established terminology in Prisma context. > > * We always use "mandatory" in this context to describe them being "non optional". > * "null"...

This one seems hairy to resolve, just spent a bit of time comparing old and new versions. I'd actually close it because it it's about behaviour of Prisma 2.X which...

Closing this since we decided to delete the entire section about behaviour pre v3: https://github.com/prisma/docs/pull/5497

Hey @lregaladohdez 👋 based on the comments from our Engineering team, I'm going to close this PR. Please feel free to reopen if you have another argument for it 🙂...

It's not quite ready unfortunately: - [ ] [Vercel examples](https://github.com/prisma/prisma-examples/tree/feat/edge-examples/deployment-platforms/edge/vercel-edge-functions) need to be added - [ ] All examples need to be tested and READMEs polished We had deprioritized [this](https://www.notion.so/prismaio/Make-sure-read-me-example-projects-for-all-Edge-deployments-423eebf368be49619b74c0a37935acbc?pvs=4)...

I'm reopening this issue so that it's on our radar and can get fixed in the CLI.

This seems to be a bug with the Upgrade CLI indeed. I believe you should be ab le to fix it by manually adjusting the indices from `@@index([application])` to `@@index([applicationId])`,...

Ah, you probably need to go through a similar process with the `fields: []` argument inside the `@relation` attribute, i.e. change `@relation(fields: [application]), references: [id])` to `@relation(fields: [applicationId]), references: [id])`,...

I realized that we needed to add one more instruction to the output of `init` that tells people to also set the `provider` field properly. So I added that and...

This seems to be a bug in the Upgrade CLI indeed. It thinks the foreign key of the relation is define n the `File` table when in fact it is...