| Summary: | Provide an option which prevents removal of still referenced objects (referential integrity) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | Erwin Betschart <erwin> | ||||||
| Component: | cdo.core | Assignee: | Eike Stepper <stepper> | ||||||
| Status: | CLOSED FIXED | QA Contact: | Eike Stepper <stepper> | ||||||
| Severity: | enhancement | ||||||||
| Priority: | P3 | CC: | caspar_d, Michal.Tkacz, stepper | ||||||
| Version: | 4.0 | Keywords: | noteworthy | ||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | Power to the People | ||||||||
| Attachments: |
|
||||||||
|
Description
Erwin Betschart
Doesn't this duplicate bug 315407 and bug 316421 ? The way I see it, we just don't have a server-side check preventing removal of reference targets. IMO such a check (as I suppose Eike has implemented in his patch for bug 315407) would solve all 3 issues... Or are there subtle differences that I'm not thinking of? The boolean configuration property of the server to control this behaviour is IRepository.Props.ENSURE_REFERENTIAL_INTEGRITY = "ensureReferentialIntegrity". The same property is used to control the behaviour of bug 315407. Rebasing all outstanding enhancements requests to version 4.0 Created attachment 173443 [details]
Patch v1
Created attachment 173474 [details]
Patch v2
Committed to HEAD Available in R20110608-1407 |