# Decision: table names come from the Object child

`digestPlan` built its table list by reading `Database`/`Schema`/`Table` attributes off `<IndexScan>` and
`<TableScan>` elements. Real ShowPlan puts those attributes on the `<Object>` child. The production plan with 51
objects therefore digested to **zero tables**, and the analyst model was asked to fix a query whose tables it could
not see.

The fix reaches into the child: the scan's own attributes, else `<Object>`. The third fallback level that looked
plausible in theory turned out to be dead code and was deleted rather than kept as insurance.

Pinned by a test using the real element shape, and visible in the measured difference: 0 tables before, 37 after.

Related: [[Max nested tags for real plans]], [[ShowPlan digest]].