Open Bug 669461 Opened 13 years ago Updated 13 years ago

Provide prior-warning if an object is in use and cannot be deleted

Categories

(Mozilla QA :: Case Conductor-Platform, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

People

(Reporter: carljm, Unassigned)

Details

For a number of types of object, the error "deleting.used.entity" is returned if deletion is attempted but the object is referenced by other objects. It is often not feasible for the UI to determine in advance whether an object is "in use" by other objects (in some cases it would be possible, but would require numerous API calls per object), which leaves us with no option but to display the deletion icon in all cases, and the user will get an error if they try to delete a used object. It's poor UI to give the user an action icon they can't actually use successfully; it'd be better if the user knew in advance which items are deletable and which are not. This would require the platform to return with each object something like a "deletable" or "in_use" boolean data attribute.
Since getting to this information requires multiple calls to various entities, it's not feasible to implement ahead of time for every retrieved entity. Because ratio of gets vs updates is, probably, going to be 100 to 1 or even more over time, this enhancement will bring down overall performance, and, therefore, won't be implemented...
Fair enough. If acquiring this information on the platform side is expensive, the alternative would be to provide a call to specifically get this information when it is needed, without risking an actual deletion. Or we just live with the poor UI.
Sure, we can do something like that...
You need to log in before you can comment on or make changes to this bug.