2008/9/23 Thomas Hechelhammer <thomas.hechelhammer@t-online.de>
Duncan Lithgow schrieb:
> 2008/9/22 Thomas Hechelhammer <thomas.hechelhammer@t-online.de>:
>> Man sollte nach dem Datenimport jedoch nach Familiennummern (F0000xx)
>> sortieren um Dubletten auszuschließen, eine Schwäche von Gramps.
> Was macht GRAMPS mit dubletten? Ich ferstehe nicht problemen.
> Duncan
Months ago I've imported a gedcom file into an existing gramps-database.
All imported people have got new I-Numbers, but gramps ignored the
family numbers.

Working only with gramps it doesn't matter that you have two equal
family numbers, but when you export them into a gedcom-file (I need this
for printing family-trees on another computer) the families are messing up.

duplicate gramps ids are errors in all cases and (can) lead to errors in coding and errors in storing under some conditions. Most code now works on the internal database handle users don see, but some code still uses the fact that the id should be unique.

So a bug submission would be the way to go with a way to reproduce the issue.


PS: just for clarity, if import ever supports merge, then equal gramps id would not trigger this (as everybody starts with user I00001), but equal database handle (or in gedcom _UID) would.

You need to look at the family-numbers if some appear twice.

-- Thomas

This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
Gramps-users mailing list