Comment 4 for bug 702620

On Thu, Jan 27, 2011 at 3:56 AM, j.c.sackett <email address hidden> wrote:
>> *is no other way to delete*.
>
> I don't think that's the case though--the artifacts that block (that I
> see) are stacked_on branches, which can be deleted, and merge proposals,
> which also can be deleted. All the other linkages should be removed when
> you use lp_delete or similar, since the exported delete method is
> destroySelfBreakReferences.

stacked on branches cannot be deleted if they are owned by someone
else; ditto merge proposals.

>> It is possible to manually delete all artefacts first, but that's a
> headache.
>
> but I think in a scripting environment it's not too much to ask so that
> we don't have accidental deletions across the webservice, where it's
> much harder (and weirder) to pop up a message to the effect of "you have
> delete a bunch of other stuff! are you sure?"

And yet if someone writes a manual iterator, isn't the end effect identical?

p-Rob