referentialIntegrity GA

[janpio]

Internal Notion document

Necessary

Issues we need to close before GA (or move to the optional section below):

• Preview feature feedback: referentialIntegrity #9380
• Rename the feature to “Prisma relation mode” → relationMode #15601
• referentialIntegrity/relationMode preview feature (referentialIntegrity = "prisma"): Make NoAction a synonym/alias of Restrict for the emulation, for all databases except PostgreSQL & SQLite. #15655
• Stabilize referentialIntegrity #10807
  • Expand tests around referential actions and referential integrity #10806
• Add autocompletion for property of relationMode (previously referentialIntegrity) in the datasource block language-tools#991
• Redo referentialIntegrity/relationMode docs docs#3832

Bugs to figure out or fix

Confirmed

Client team

• Update Restrict failed on prisma referentialIntegrity #13766
• _count doesn't update in many to many relation #12557
• Prisma Client upsert returns count instead of data #10935
• referentialIntegrity=prisma: Delete parent relation failing when using composite id #10000
• OnUpdate default referential Integrity action while using Prisma to handle referential Integrity #10581

Schema team

• Validation fails to detect invalid SetNull referential action referencing non-optional fields #14673
• Re-Introspection: referentialIntegrity = prisma not respected when using @@map() #11022
• MySQL does not support onDelete: setDefault #11498
• Network latency increases with selecting nested relations #12582 (probably unrelated to feature)
• Switching between referentialIntegrity modes makes migration history obsolete #15225

Unconfirmed

• Unable to delete Obj1 if Obj2 references it with Action: SetNull #14271
• Prisma error: Explicit many to many relationship when updating model #12378
• Cannot update a table - code: 'P2021' #12256

Unknown

• Foreign key indexes are not well changed by prisma #12288

Already fixed/closed before we started GA work

• PANIC: Expected record selection to contain required model ID fields.: ConversionFailure("\"c266149d-e045-4db5-bee4-3e49f3252e65\"", "Int") in query-engine/core/src/interpreter/interpreter.rs:68:26 #11191
• Planetscale not able to upsert with Prisma #11469
• referentialIntegrity = prisma: Broken query on onUpdate: Cascade | symbol ... not found | The column ... does not exist in the current database. #10758

Features to decide

• Automatically create an index on @relation by default, add new option for disabling - for referentialIntegrity/relationMode = prisma #10611
• Recommend adding indices to foreign keys when referentialIntegrity = "prisma" language-tools#992
• Suggestions/Recommendations for schema validation / VS Code extension #10173
• Suggestions/Recommendations for schema validation / VS Code extension (referentialIntegrity = prisma, Indexes) language-tools#946

Internal

• Undo "skip flaky referentialActions sql server test" #7936
• Client tests for Vitess, with relationMode=prisma #6927

Optional

Issues that could wait until after GA:

• Support (some) weak relations with no foreign key #7351
• Support for schema definitions that are not overwritten by a prisma db pull #9571
• Introspection: Give advice if introspection result does not include any relations #1469
• Improve situation when referentialIntegrity=prisma and existing migration file (with FKs) fails #10843
• Relations over composite types #10102

[janpio]

Released with 4.7.0. Documentation at: https://www.prisma.io/docs/concepts/components/prisma-schema/relations/relation-mode