# Aggregate each detail table before joining two totals

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Aggregate each detail table before joining two totals

ID: MHC-D-RESEARCH-9719 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/aggregate-each-detail-table-before-joining-two-totals

A join can inflate both totals at once.

Knowledge source release: MHC-RPUB-20261112-20287590
Source corpus commit: 20287590ddd3999b7492df232822b6a0f7d114b1
Source manifest SHA-256: 2a987660d12de0ce2bde77a421424f7762af1ff77872ef41093fecc33db74a95
Source projection SHA-256: 2807da39bbe6a3dee2db32a76675ac5185f5a33e8b0a5cdd0c22a4731f3378a0

### Use when

- Two one-to-many detail tables are both joined to the same parent.

### Avoid when

- Pre-aggregation can erase needed invoice-payment pairings. An absent or NULL total needs a stated meaning; do not silently replace it with zero.

### Explanation

When the report needs one total per parent, sum each child set by the same complete parent key before joining. Use LEFT JOIN if parents without child rows must remain. Do not sum multiplied detail rows and expect GROUP BY to repair the totals.

### Steps

1. Compute invoice and payment totals independently by customer, with the same intended filters.
2. Keep child row and non-null amount counts alongside totals when missing data must be distinguished.
3. Check known totals, missing child records and missing amounts before assigning any zero defaults.

### Example

Four invoices totalling 100 and three payments totalling 18 can yield sums of 300 and 72 in a detail join. Separate aggregates retain 100 and 18.

### Check

Totals match the independent sums, required parents survive, and missing-data cases remain distinguishable from a recorded zero.

### Limits

- Pre-aggregation can erase needed invoice-payment pairings. An absent or NULL total needs a stated meaning; do not silently replace it with zero.

### Evidence and sources

- supports: In PostgreSQL, a qualifying join produces an output row for each matching row pair; joining two independent one-to-many detail tables through the same parent can multiply rows before aggregation. — pg-joins. Claim limit: This describes row multiplicity, not a universal query planner rule; choose aggregation only when the report needs one total per parent, and preserve row pairings when they are meaningful.
Source reading history: selected_passages; 2026-10-11; Sections 7.2.1.1 Joined Tables; 7.2.1.3 Subqueries; 7.2.2 WHERE; 7.2.3 GROUP BY. Version 18 passages rechecked on 2026-10-11: matching row pairs, full ON conditions, derived tables, filtering and grouping. Grounds SQL semantics, not every engine's behavior or the effectiveness of the drafted reporting workflow.
Agent release review: PostgreSQL 18 table expressions, NULL comparisons and aggregates, the UK Government Data Quality Framework and Microsoft Power Query profiling documentation were checked at the cited sections. The original examples and scope limits remain attached. (Sections 7.2.1.1 Joined Tables and 7.2.1.3 Subqueries)
- supports: In PostgreSQL, LEFT JOIN adds a row with NULL right-hand values when no pair satisfies ON. A later WHERE condition keeps only rows for which it is true; a right-hand equality test rejects these NULL rows, while a NULL-accepting condition can retain them. — pg-joins. Claim limit: PostgreSQL 18 logical row semantics, not a planner or performance guarantee. A NULL-accepting WHERE condition does not recreate rows already lost because their key matched only nonqualifying right-hand records.
Source reading history: selected_passages; 2026-10-11; Sections 7.2.1.1 Joined Tables; 7.2.1.3 Subqueries; 7.2.2 WHERE; 7.2.3 GROUP BY. Version 18 passages rechecked on 2026-10-11: matching row pairs, full ON conditions, derived tables, filtering and grouping. Grounds SQL semantics, not every engine's behavior or the effectiveness of the drafted reporting workflow.
Agent release review: PostgreSQL 18 table expressions, NULL comparisons and aggregates, the UK Government Data Quality Framework and Microsoft Power Query profiling documentation were checked at the cited sections. The original examples and scope limits remain attached. (Section 7.2.1.1 LEFT OUTER JOIN and ON-versus-WHERE example; Section 7.2.2 WHERE)
- supports: COUNT(*) counts rows while COUNT(expression) counts only input rows with a non-null expression. — pg-agg. Claim limit: Scalar expression counting in PostgreSQL 18. These are counts of input rows, not automatically distinct entities or valid field values; join and filter rules determine the input. No planner or performance guarantee.
Source reading history: selected_passages; 2026-10-11; Section 9.21, Table 9.62: count and sum; paragraph on aggregates with no selected rows. PostgreSQL 18 count and sum definitions, including empty-input behavior, rechecked on 2026-10-11. Selected passages ground the row/value/total distinction, not production execution or the effectiveness of the drafted reporting workflow.
Agent release review: PostgreSQL 18 table expressions, NULL comparisons and aggregates, the UK Government Data Quality Framework and Microsoft Power Query profiling documentation were checked at the cited sections. The original examples and scope limits remain attached. (Section 9.21 Aggregate Functions, count)
- supports: In PostgreSQL 18, SUM adds non-null input values; if no rows are selected, it returns NULL rather than zero. — pg-agg. Claim limit: Group creation and join type are separate questions. A NULL sum alone does not establish the cause of missing data or a numerical zero; scalar totals also do not establish that all input amounts were present.
Source reading history: selected_passages; 2026-10-11; Section 9.21, Table 9.62: count and sum; paragraph on aggregates with no selected rows. PostgreSQL 18 count and sum definitions, including empty-input behavior, rechecked on 2026-10-11. Selected passages ground the row/value/total distinction, not production execution or the effectiveness of the drafted reporting workflow.
Agent release review: PostgreSQL 18 table expressions, NULL comparisons and aggregates, the UK Government Data Quality Framework and Microsoft Power Query profiling documentation were checked at the cited sections. The original examples and scope limits remain attached. (Section 9.21, Table 9.62 sum and paragraph on no selected rows)
- pg-joins: PostgreSQL 18: Table Expressions — https://www.postgresql.org/docs/18/queries-table-expressions.html
- pg-agg: PostgreSQL 18: Aggregate Functions — https://www.postgresql.org/docs/18/functions-aggregate.html

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
