SQL GROUP BY Silently Excluding NULLs: How to Catch and Fix It

SQL GROUP BY treats all NULL values in the grouping column as a single group, so they do appear in the result set together. However, NULL values inside the aggregated column are still silently ignored by functions like SUM and AVG, which can make your totals look correct while they are actually understated.

COUNT(column) counts only non-NULL values in that specific column, while COUNT(*) counts every row in the group regardless of NULL. The difference between the two numbers tells you exactly how many NULLs exist in that column within each group.

Use COALESCE(column, 'Unknown') or a CASE expression on the grouping column to replace NULLs with a meaningful placeholder before grouping. Alternatively, use GROUPING SETS or a UNION ALL with a separate NULL filter to explicitly surface those rows in your output.

Yes. A LEFT JOIN produces NULL in columns from the right table when no match is found, and if you then GROUP BY or filter on one of those nullable columns, those unmatched rows can disappear silently. Always inspect row counts before and after a join when NULLs are possible.

Yes, the SQL standard specifies that NULLs in the grouping column are collected into a single group, and all major databases including PostgreSQL, MySQL, and SQL Server follow this behavior. The trap is consistent across engines, so the detection and fix patterns described here apply everywhere.