Client side cascade delete
Ivan Misyats commented
it would be great to fix this. It is very annoying.
I'd appreciate if this was fixed.
Thanks for your effort, guys
Ward Bell commented
Sorry. Just have not got to it. There is a work around (not great) and we're working higher priorities. This is an open source project. We'd welcome your attempt at it and a PR.
More than 2 years... and still nothing new on this one?
Pavel Pikat commented
Any updates on this?
Duncan Grist commented
We've looked into how we could patch something on top of breeze to do this automatically, but because the foreign keys on dependent entities are NULLed before we get any event fired, it's complicated and messy to work out what entities should be detached/deleted when a parent entity is removed.
So we would also very much like to see this behaviour as part of the core.
fix this as well as many to many. come on Breeze devs!
David Manning commented
This would make life a lot easier. +1
Steve, Jay, Ward.
This is a pressing issue for us (We write our CTOR's with custom delete logic for each entity with childs)
Cascade info. should be passed to the metadata so the client can support it.
Ran Rosenmann - Yayasoft
Joe Warwick commented
Cascade delete is exposed by the entity framework schema., so it is possible to provide this from metadata.
I understand that breeze does not want to get into the referential integrity space a whole lot, but this particular item would greatly simplify client side model decorators.
This is really needed when using DB cascaded deletes which is very common in one-to-many relationships...