[SERVER-1298] ON DELETE, ON CASCADE for DBRef Created: 25/Jun/10 Updated: 02/Jun/23 Resolved: 23/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Usability, Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Leon van der Veen | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 5 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
I love the way MongoDB handles data. But there is no mechanism for 'foreign keys' in the way like sql, what is a must have. I mean, there should be a mechanism we can delete items automatically if a DBRef becomes null Is it possible to do this (easily) ? |
| Comments |
| Comment by Tobi N/A [ 02/Jun/23 ] |
|
I created a new ticket for this, since transactions on sharded clusters work nowadays https://feedback.mongodb.com/forums/924280-database/suggestions/46728697-cascading-delete-for-dbrefs |
| Comment by Ian Whalen (Inactive) [ 23/Jun/15 ] |
|
Hi Leon, thanks a lot for filing this feature request and apologies for the time since it was last updated. We're going to close this ticket as "Won't Fix" given the constraints around making this work seamlessly in a sharded cluster. |
| Comment by Eliot Horowitz (Inactive) [ 25/Jun/10 ] |
|
The big problem is how this interacts with sharding, since a ref may point to something on a different server. |