There is an idea to make a conclusion of the family tree data. Assume that the data is entered from top to bottom and there are no additional branches yet, just a Christmas tree, i.e. neither mistresses nor stepfathers yet. The following questions
1. How to implement intergenerational and intragenerational binding? 1.2 Suppose that when filling in the table I immediately bind the spouse to the spouse ID, and in the spouse line I specify the offspring ID, but then later there will be difficulties in specifying children not from this spouse. 2. How best to fill the base? Make 1 table with data about people and 2 table with data about connections, or can you think of something here?
Maybe someone has a ready-made suitable script, or someone stumbled upon a similar algorithm? I will be glad to any help))
OK, I'm making a table of families
famID int(11) // PRIMARY KEY wedding date //ΠΠ°ΡΠ° ΡΠ²Π°Π΄ΡΠ±Ρ divorce date //ΠΠ°ΡΠ° ΡΠ°Π·Π²ΠΎΠ΄Π° dive tinyint(1) //Π‘ΠΎΡΡΠΎΡΠ½ΠΈΠ΅ Π±ΡΠ°ΠΊΠ° father int(11) // ID Π½ΠΎΠΌΠ΅Ρ ΠΈΠ· individuals mother int(11) // ID Π½ΠΎΠΌΠ΅Ρ ΠΈΠ· individuals
And the table of individuals
1 ID int(11) // PRIMARY KEY 2 name varchar(50) //ΠΠΌΡ 3 firstname varchar(50) //Π€Π°ΠΌΠΈΠ»ΠΈΡ 4 gender char(1) //ΠΠΎΠ» 5 birth date //ΠΠ°ΡΠ° ΡΠΎΠΆΠ΄Π΅Π½ΠΈΡ 6 death date //ΠΠ°ΡΠ° ΡΠΌΠ΅ΡΡΠΈ 7 comment varchar(200) //ΠΠΎΠΌΠΌΠ΅Π½ΡΠ°ΡΠΈΠΈ 8 famC int(11) //famID
So, families
will display all connections, if this is a husband and a wife, then a famID
number is assigned. If their child, then individuals
recorded in famC
family number of parents. It seems to work ...