#19 Ghost names

closed-fixed
None
5
2001-11-09
2000-11-17
No

merge_indi does not properly delete all names
if the user has edited the combined record
during merge, and removed some names.

I suspect that REFNs will exhibit the same bug,
and probably the merge routine for families as
well.

Workaround to avoid bug is to save the
combined record as is, then edit it after merge
is done.

Workaround to fix the bug (db with ghost names) is
to save db to gedcom and load it back to a new
db.

Discussion

  • Anonymous - 2000-11-20

    I think the thing to do is to classify
    the difference between the new node (node04)
    and the old node (node2) and delete any
    different names only in the old one.
    However, they may also be in the old node1,
    so we must check that that it will survive
    if node1 also tries to delete the same
    NAMEs & REFNs.

    Alternatively, we could spend a second classify
    to find out which ones were in node2 but not
    node04, and ALSO not in node1.

     
  • Anonymous - 2000-12-07

    I have just coded & tested the fix for this,
    but have not yet added it to the repository.

     
  • Anonymous - 2000-12-13

    Added fix to repository.
    Technical summary:
    classify new vs old, not classify original1 vs original2

     
  • Anonymous - 2000-12-13
    • status: open --> closed-fixed
     
  • Anonymous - 2001-11-09
    • assigned_to: nobody --> puddle
     

Log in to post a comment.