Hi,
We are creating a chassis manager that creates/deletes elements and encountered an issue when trying to delete an element. To do this in QAction, you first have to request the element, but the request failed because the protocol of this element had been deleted on the DMA.
First we assumed this was a bug in the code library, but then we wondered "Why is it possible to delete a protocol that's used by one or multiple elements?". It is not possible to create an element without defining a protocol, but it is possible to assign a random protocol to an element and delete that protocol afterwards. The result is the same.
If you want to delete a protocol, this message appears to you:
Shouldn't this pop-up message make it impossible for users to delete a protocol that's in use?
I follow your reasoning Stijn. With what we know today I agree we should no longer allow this. Changing a protocol on an element is definitely not supported, but this option opens the door to achieve this.
In my search for a reason why we would have done it like this in the past... I can only think that it was to keep the fault and performance data for those element. (in MySQL the tables and data was dropped upon deletion of the element, with Cassandra it is not phased-out).