On Mon, Aug 23, 2010 at 9:46 AM, Raivo Kask <raivo.kask@...> wrote:
> Doug Blank <doug.blank <at> gmail.com> writes:
>> On Mon, Aug 23, 2010 at 6:37 AM, Raivo Kask <raivo.kask <at> gmail.com> wrote:
>> > Duncan Lithgow <duncan.lithgow <at> gmail.com> writes:
>> >> That shouldn't happen. The gramps ID we see is tiot the one that
>> >> gramps uses internally.
>> >> Duncan
>> > But it happens ... ID for Places and Event are related to persons.
>> > The should instead be unique as the rest of ID:s in the database.
>> Seems like there is some confusion here about ... something. Not sure
>> what you are doing. Some points:
> OK - I'll try to explain what I did and what I wanted to do.
> I got a huge database (1 500 people) from a relative. That database was created
> in a Mac environment with some Mac software and was exported to me.
> I imported that Mac database into Gramps without any problems.
> Since I was only interested in 2 family trees (mmm and fff) in that Mac database
> I then exported those 2 family trees (mmm.gramps and fff.gramps) from that Mac
> database and started to update mmm.gramps and fff.gramps separately, i.e. loaded
> mmm.gramps and made my updates, loaded fff.gramps and made my updates.
> After a while I discovered that persons belonging to both mmm.gramps and
> fff.gramps were only updated in one database. I thought Gramps kept track of
> persons belonging to both mmm.gramps and fff.gramps ... which was not the case.
> I realized my mistake and tried to merge mmm.gramps and fff.gramps into a single
> database by creating an empty database, importing mmm.gramps and then importing
> fff.gramps into the same database. Then I got messages that some of ID:s for
> Persons, Places and Event were identical.
Ok, it sounds like you now understand how Gramps works.
> OK - I resolved this issue manually for conflicting ID:s.
> To me it seems strange that Gramps will not keep track of conflicting ID:s. What
> I mean is that when I run Gramps all the family trees are keep in memory and it
> should be easy to check if a conflicting ID is entered. As it is now I can load
> a family tree, create an Event with an ID that already is in the database for
> another family tree. I don't see the advantage by having the option to create
> identical Event ID for separately family trees.
Having Gramps keep track of all IDs across all of your databases would
be a huge task, and against the way that other people use gramps. For
example, I sometimes use Gramps to open, edit, and export other
people's trees. It may seem strange to you, but Gramps is designed to
work in a way that is general and useful to a large range of tasks.
Hope that helps, and good luck,
> This SF.net email is sponsored by
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> Gramps-users mailing list