This repository has been archived by the owner on Sep 2, 2022. It is now read-only.
Support cascading delete with deleteMany #1936
Labels
Comments
|
Still waiting for... |
|
@marktani - Is there an ETA on this feature? |
|
@marktani any updates? :) |
marktani
changed the title
|
I stumbled upon this issue by running into the "The change you are trying to make would violate the required relation" error, would love to see support for this! |
|
Any progress on this? |
|
Is there any progress on this? In the mean time does anyone know of a sensible work around? This is a huge blocker for me 😞 |
|
Waiting for this one, would be useful in our production. |
|
We really need help on features like these (and basic text search). |
ddowl
referenced
this issue
in ddowl/cookbk
Mar 18, 2019
Started implementing and testing several mutators. Realized that I need to relax the schema definitions of certain functions (e.g. deleting a non-existent user can't return that user). Discovered that Prisma's Mongo connector doesn't support cascading deletes: prisma/prisma#1936 I can work around this by making sure that I delete everything in the right order, or work on setting up a Postgres DB that behaves appropriately.
|
For the SQL connectors cascading delete support for deleteMany and nestedDeleteMany will go into beta today. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current behavior
Currently cascade delete don't work with deleteManyTYPE only with deleteTYPE
Reproduction
Just create relation with
onDelete: CASCADEand run mutationdeleteManyTYPEExpected behavior?
Cascade delete work with both deleteManyTYPE and deleteTYPE
The text was updated successfully, but these errors were encountered: