Upgrade to Prisma ORM 6 - null/undefined behavior change #6752
Description
In the Prisma Client docs (Fields & types -> Null and undefined), it mentions that there's a shift in behavior between Prisma ORM 5.19.1 or earlier and version 5.20.0 with a feature flag.
Later in the page, it says:
This new behavior is intended to become the default in Prisma ORM 6.
Since many folks rely exclusively on the upgrade guide when bumping major versions, they can easily miss the breaking change (if it's actually been enabled).
Could you please add a section to the "Upgrade to Prisma ORM 6" about this if it's now the default, or update the "Null and undefined" section about Prisma 6?