I ran Set Relationships (SR) on an end-of-line ancestor who has no known spouse and he is the only one designated. I repeated on his son, also having no known spouse, and his father and siblings are designated but not his descendants (total of 5 relationships) . None of his siblings have descendants in this tree but if SR on one of the siblings, then his descendants are designated (332 relationships). Down one more generation and SR on the only child having descendants and also without a known spouse and just the ancestors, siblings and a spouse of the latter got designated (17 relationships) - none of his children! SR on any of the children generates 332 relationships - those having descendants have known spouses in the parent-child family.
This is not an EOL or near-EOL issue. It happens mid-line as well wherever there is an unknown parent in the line of descent.
It was not a problem in RM7 or in RM9 - I checked superficially.
Iâm pretty sure it is systemic and not peculiar to my database so a confirmation would be welcome.
Given that the problem is spouse related, perhaps there is a connection between this problem and that fact that the new âSpouse ofâ feature in Set Relationships in 10.0.1.0 will sometimes override an actual blood relationship. So perhaps the absence of a spouse is causing the new Set Relationships to terminate its scan for descendants prematurely.
I continue to suspect that the best solution would be to go back to the pre-10.0.1.0 Set Relationships as a baseline. Then add the âSpouse ofâ feature back in to the previous baseline by making a second pass at the database as a part of the Set Relationships process, looking for individuals who are not related but who are the spouse of someone who is.related. The second pass would be an almost trivial piece of code and it would run extraordinarily fast. You wouldnât notice any extra time in Set Relationships. I have done it already in a test database using an SQLite script. And going back to the pre-10.0.1.0 Set Relationships code as a baseline should solve this new problem as a useful side effect in addition to solving the problem of âSpouse ofâ relationships sometimes overriding actual blood relationships.
Not really. I have lots of people in my database with only a single parent - sometimes a father and sometimes a mother. I donât have to enter a dummy âunknownâ person as the other parent.
If RM cannot discern if Spouses are related somewhere back in their lines and/or how children of a Father by two different Spouses affect relationships, it seems like a difficult problem.
If SR is applied to a single parent, no direct relationships are set for the descendants, regardless of being mother or father. There may be an indirect relationship set - I havenât looked into it yet.
The breakage in the direct line at a single parent may account in part for reports of longer paths than expected being reported. But we do not know how much there is in common among the calculating algorithms of Set Relationships, Relationship Calculator, Kinship List, Descendant Chart, âŚ
Yeah, my thinking in that original post was that âŚwithout the actual Mother (egg donor) as a given⌠all descendants of this Unknown Mother are conditionally being left uncalculated. If it happens with Unknown Father, too, that sounds algorithmic in nature.
I just changed the person for Set Relationships in my database. When i choose a pwrson with a spouse it seems to go through all descendants with no issue. When I choose a person with an unknown spouse it didnât for her son or any of his descendants. It did set for ancestors. Just a quick lok at just a few generations
I can test some examples- I will make copy of current database to test.
My son-in-law and daughter are about 12th cousins via 2 different paths (just learned that recently)
I guess it might depend on what /when RM assigns â by path distance vs blood etc.
Confirming issue with Set Relationships and Kinship List with focus person as a single parent has been reported to development.
The Descendant Chart always has the line coming from the spouse. Iâm not seeing an unknown spouse showing which would prevent the missing line. That has also been reported to development.
Itâs not that the focus person is a single parent. Rather, the break occurs anywhere in the direct line of descent from the focus person of Set Relationships. I happened to come across the omission by focusing on an end-of-line single parent. At first, I thought it might be EOL dependent but further testing and checking the contents of the PersonTable with sqlite led me to the observations Iâve reported.
Not sure if this is a contradiction of the alleged issue: My father had a son with an unknown mother (not my own.) On my 10.0.1.0, I set relationships to myself (as usual). RM correctly shows the son as a half-brother to me, and his daughter as a half-niece.
Is the unknown mother entered as a dummy person, perhaps with a name such as âunknownâ? Or is the unknown mother left null?
If the unknown mother is left null, then it appears to be a contradiction of the alleged issue. But there still seems to be ample evidence that the alleged issue is real. Sometimes there can be very subtle and hard to discover differences where a problem will manifest in some cases but not others.
What happens IF you set relationship to your Dad or to the half- brother? or even better unlink your Mom from your Dad and then set relationship-- think in your case, since your Dad has one spouse listed, it is going to show the relationship to your half-brotherâas Tom pointed out that when he set relationship on his son ( who had only one parent Listed), also having no known spouse, and his father and siblings are designated but not his descendants (total of 5 relationships)
You are correct. When I actually deleted the nameless mother as a person, and then set relationships to the father, the son and daughter showed up only as distant (tenth) cousins - which is interesting in a different sense and worth my following up.
Itâs not a contradiction. The break in lineage only happens at an unknown spouse of the focus person or in his/her descendancy. In your example, the focus person has no unknown person in his descendancy. Change the focus person for SR to his father and the half-brother will not show as such, provided the unknown spouse has no RIN other than 0.
