You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Optimization of Data Structure
A family tree is a model with continuously growing data and an infinite total set, making it unsuitable to store child node IDs within parent nodes. Instead, it is recommended to adopt a structure where child nodes carry parent node IDs. This design better aligns with the dynamic nature of family trees and supports modern data query technologies like GraphQL.
Handling Multiple Parent Relationships
In some cases, a child node may have multiple parent pairs (e.g., biological parents and adoptive parents). To accommodate this complexity, it is suggested to clearly designate a "primary parent" within the child node’s parent ID field. This allows for prioritization based on cultural or legal requirements.
Support for Multiple Spouses and Child-Parent Marriage Association
The current model does not adequately handle scenarios involving multiple marriages or concurrent spouses (e.g., polygamy or polyandry). It is recommended to extend the model to support multiple spouse relationships and ensure that children can be clearly associated with a specific spouse pair. For example, a field could be added to child nodes to explicitly link them to a particular marital relationship (e.g., marriage ID or spouse pair ID), ensuring accurate representation of complex family structures and bloodlines.
I try to set a person node who married twice(two outsiders),the charts seems unreasonable
The text was updated successfully, but these errors were encountered: