Hi,
As part of maintenance operations on the DBB metadatastore, we had to delete Collections.
You would think that deleting a Collection would also delete all the buildResults of this Collection... but this is not the case, and apparently you have to delete the buildResults one by one...
There are also likely other logical dependencies that should be handled by the DBB API when deleting a parent object, and across multiple dependency levels.
Perhaps a "logical delete cascade" option should be included in the deletion of a Collection to delete in cascade, and upon explicit request, all associated buildResults.
Do I have to open an upgrade request on the IBM Ideas site for this?
Thanks.