HelpDatabase Reference › Match_TreeOverride

Match_TreeOverride Table

The Match_TreeOverride table overrides a specific match’s gathered tree with a better tree — for example, a GEDCOM upload that is more complete or accurate than the small tree gathered from the service. When common ancestors are computed, the override tree is used in place of the match’s own gathered tree.

Each match has at most one override. Setting an override removes any existing override for that match first, so the table holds one current override per MatchGuid.

Column Reference

ColumnTypeDescription
Idint (PK)Auto-incrementing primary key
MatchGuidstringThe match whose tree is being overridden
CompanystringWhich service the match belongs to
OverrideTreeIdintDGTree.Id of the better tree (e.g., a GEDCOM upload)
AssignDateDateTimeWhen the override was set (UTC)
NotesstringOptional free-text notes about the override (nullable)

How It’s Populated

When a user overrides a match’s tree, the application deletes any prior override for that MatchGuid and inserts a new row with AssignDate set to the current UTC time. OverrideTreeId references a DGTree record, which is then substituted for the match’s gathered tree during common-ancestor computation.

Related Tables

  • DGTree — the better tree referenced by OverrideTreeId.
  • Kit_TreeAssignment — assigns the user’s “my tree” for a kit; overrides apply to the matches on the other side of the comparison.
  • Computed_CommonAncestors — cached common ancestors that use the override tree when one is set.