OOPS when trying to delete stacked-on branches.

I haven't actually confirmed this yet. Just want to make sure it's being tracked.

I'd expect that they can't be, because the +delete code doesn't know how to clear the stacked_on foreign key reference. But I haven't checked either.

So it turns out that if you try to delete the stacked on branch, you get an OOPS:

Retry: update or delete on table "branch" violates foreign key constraint "branch_stacked_on_fkey" on table "branch"<br /> DETAIL: Key (id)=(77) is still referenced from table "branch".<br /> <br />

This isn't good, though probably better than allowing the branch to be deleted...

I just got a similar OOPS. The table is different, but this may be a storm issue from the same bug.

OOPS-1060EA133:

Traceback (most recent call last):

    * Module zope.publisher.publish, line 141, in publish
      publication.handleException(
    * Module canonical.launchpad.webapp.publication, line 445, in handleException
      raise Retry(exc_info)

Retry: update or delete on table "branch" violates foreign key constraint "branchrevision__branch__fk" on table "branchrevision"
DETAIL: Key (id)=(26850) is still referenced from table "branchrevision".

Deferred to Feb since package branch work has taken higher priority.

Despite the ugliness of the behaviour, not a high priority bug since deleting stacked-on branches will always be forbidden (just in slightly nicer language).

PUNT!

Fixed in RF 7740.