From: Earney, Billy C. <earney@um...> - 2003-11-03 15:14:34
I like the second option. The more normalized we can make the database
From: Lorenzo Cappelletti [mailto:lorenzo.cappelletti@...]=20
Sent: Saturday, November 01, 2003 6:45 AM
Subject: [Gramps-devel] Re: Post-1.0 - moving to a real database
Don Allingham <dallingham@...>, Wed 29 Oct 2003 17:22
> need them. The person/family objects are going to have to be
> fixed. Currently, families keep a list of people, and people
> keep lists of families. This will have to be changed so that=20
I'm not an expert in databases either, but I think you've got two=20
1) A list of individuals: a family table has got the columns such as ID,
father, mother, child1, child2, child3,... This solution implies a=20
fixed number of child columns which may waste space if too high or be=20
problematic if too low.
2) Table of individual-family pairs: there are three tables, one for the
families, one for the individuals, and one that binds individuals to=20
families. The latter has got only two columns: IndividualID and=20
FamilyID. This way, a family may have any number of individuals and an=20
individual may belong to an arbitral number of families. Because a real
database engine is optimized for searches like these, performance should
be very high.
Fingerprint: 8CDD 3408 53B2 6122 99DA EE37 1523 68FC D906 4C08
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
Gramps-devel mailing list
Get latest updates about Open Source Projects, Conferences and News.