Files
sql-server-query-ai/kb/Table names live on Object.md
T
ahmed mohammedandClaude Opus 4.7 8b42a0931c docs: karpathy-pattern wiki built from the spec, plan, design contract and decisions ledger
kb/ is its own wiki root: 34 pages across 7 categories, index.md catalog, log.md, AGENTS.md schema layer, and raw/ holding copies of README, the spec, the 13-task plan, the design master and the SDD ledger.

Every page cross-references 3 to 6 others and all 107 wikilinks resolve except two [["list"]] artefacts inside JSON snippets in the copied plan.

Kept separate from the repository root on purpose: its generated graph lands in kb/.ua/ instead of overwriting the code graph.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-09-22 12:14:05 +03:00

786 B

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.