HelpDatabase Reference › AncestryAncestorCouple

AncestryAncestorCouple Table

The AncestryAncestorCouple table records the common-ancestor couples that A* identifies between you and a match — the “potential ancestors” or shared most-recent common ancestors surfaced on a match’s compare page. Each row is one couple (a father and a mother) shared between one of your kits and one match, with the details of each partner flattened into the same row.

Rows are keyed by the pair (TestGuid, MatchGuid), so there is one couple row per you/match pairing.

Column Reference

Identifiers

ColumnTypeSourceDescription
Idint (PK)AutoAuto-incrementing primary key
TestGuidstringCompareYour test kit GUID. Stored uppercased.
MatchGuidstringCompareThe matched person’s GUID. Stored uppercased.

Father’s Details

ColumnTypeSourceDescription
FatherAmtGidstringCompareA* match-tree global ID for the father
FatherBigTreeGidstringCompareA* big-tree global ID for the father
FatherKinshipPathToSampleIdstringCompareKinship path connecting the father to your sample (kit)
FatherKinshipPathFromSampleToMatchstringCompareKinship path from your sample through the father to the match
FatherPotentialboolCompareTrue if the father is a potential (not confirmed) common ancestor
FatherInMatchTreeboolCompareTrue if the father appears in the match’s own tree
FatherInBestContributorTreeboolCompareTrue if the father appears in the best contributor tree A* used
FatherDisplayNamestringCompareFather’s display name
FatherBirthYearstringCompareFather’s birth year
FatherDeathYearstringCompareFather’s death year
FatherIsMaleboolCompareTrue when a father person is present in the couple
FatherNotFoundboolCompareTrue if the father person could not be found
FatherVeiledboolCompareTrue if the father’s details are veiled/hidden by privacy
FatherRelationshipToSampleIdstringCompareRelationship label of the father to your sample
FatherRelationshipFromSampleToMatchstringCompareRelationship label along the path from your sample to the match via the father

Mother’s Details

ColumnTypeSourceDescription
MotherAmtGidstringCompareA* match-tree global ID for the mother
MotherBigTreeGidstringCompareA* big-tree global ID for the mother
MotherKinshipPathToSampleIdstringCompareKinship path connecting the mother to your sample (kit)
MotherKinshipPathFromSampleToMatchstringCompareKinship path from your sample through the mother to the match
MotherPotentialboolCompareTrue if the mother is a potential (not confirmed) common ancestor
MotherInMatchTreeboolCompareTrue if the mother appears in the match’s own tree
MotherInBestContributorTreeboolCompareTrue if the mother appears in the best contributor tree A* used
MotherDisplayNamestringCompareMother’s display name
MotherBirthYearstringCompareMother’s birth year
MotherDeathYearstringCompareMother’s death year
MotherIsFemaleboolCompareTrue when a mother person is present in the couple
MotherNotFoundboolCompareTrue if the mother person could not be found
MotherVeiledboolCompareTrue if the mother’s details are veiled/hidden by privacy
MotherRelationshipToSampleIdstringCompareRelationship label of the mother to your sample
MotherRelationshipFromSampleToMatchstringCompareRelationship label along the path from your sample to the match via the mother
Each row is a couple: the father columns and mother columns describe the two partners of one shared ancestral couple. Either partner may be absent or veiled, in which case the corresponding *NotFound or *Veiled flag is set and the name/year fields are blank.

How It’s Populated

Rows are written during a per-match Compare visit. When the compare response carries an ancestorCouples list, the app flattens each couple — pulling the father and mother sub-objects into the single-row layout above — and saves it against the current TestGuid and MatchGuid. If a match has no shared ancestor couples, no row is written. Because this happens on compare pages, the table is only populated when tree gathering (or a gather that visits compare pages) is enabled.

Data Preservation Rules

Saving is an upsert keyed on (TestGuid, MatchGuid): the app looks for an existing row for that pairing and updates it in place if found, otherwise inserts a new one. A unique index on (TestGuid, MatchGuid) enforces one couple row per you/match pairing, so re-gathering refreshes the existing row rather than duplicating it.

Related Tables

  • Ancestry_matchGroups — the master match record this couple is associated with, via MatchGuid.
  • Ancestry_matchTrees — the individual people in the match’s tree, where these common ancestors also appear.
  • Ancestry_TreeData — per-person tree summary metadata for the same trees.