[erlang-bugs] table referred to by foreign key does not have node pool properly cleaned up when a node is removed from the schema

[Paul Mineiro]

the attachment has a minimal demonstration.

this bug causes substantial problems trying to maintain the table going
forward since (as indicated in the attachment), manual maintainence of the
node pool list is also not possible once this occurs.  if we had not been
able to create a machine that had the same node name as the one removed,
i'm not quite sure how we would have navigated around this in our
production system, short of restore from backup.

i'm using mnesia-4.3.5 and erlang-otp r11b5.

thanks,

-- p

In an artificial world, only extremists live naturally.

        -- Paul Graham
-------------- next part --------------
A non-text attachment was scrubbed...
Name: foreign-key-bug.sh
Type: application/x-sh
Size: 2684 bytes
Desc: 
URL: <http://erlang.org/pipermail/erlang-bugs/attachments/20080510/eb1d04d7/attachment.sh>