Principle

Count rows and non-null values separately

A row can exist even when the invoice does not.

About 1 min read

Before you use it

Use when
  • You need to count invoices or check whether a field is filled.

Keep this limit in mind

  • Empty strings and whitespace are not SQL NULL automatically. Repeated values are counted again; define missingness and row meaning before interpreting the gap.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

COUNT(*) counts input rows; COUNT(invoice.id) skips rows where that ID is NULL. A LEFT JOIN can retain a supplier through a row with NULL invoice values, so a row count is not automatically an invoice count. Choose the count that answers the report's question.

Steps

  1. Calculate both counts for the same filters and groups; include a known case with no match.
  2. Use a field that cannot be NULL in a real invoice when counting matched invoices.

An example

A supplier with no matching invoice gets COUNT(*) = 1 and COUNT(invoice.id) = 0 in its group after a LEFT JOIN.

Check your result

For each total, name what is counted: result rows or rows with a non-null field. Neither count alone proves a distinct entity total.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingCount rows and non-null values separately

Evidence and sources
Supports

COUNT(*) counts rows while COUNT(expression) counts only input rows with a non-null expression.

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.

PostgreSQL 18: Aggregate Functions · Section 9.21 Aggregate Functions, count

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.

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.

PostgreSQL 18: Table Expressions · Section 7.2.1.1 LEFT OUTER JOIN and ON-versus-WHERE example; Section 7.2.2 WHERE

All sources (2)
Edition and review

Version 0.1.0 · Published

Edition checked · 2026-11-12

Read this idea as JSON · Release details