Strange MySQL AVG() anomaly NULL values
That's the normal behaviour, since NULL is not zero. How do you make the average of 5 + NULL? So MySQL is taking only the rows that can be averaged.
Appart from the correct answers other users have already given you, you can also use the COALESCE function, which returns the first non-NULL value you specify in the list, so you can replace the NULL one with the one you like:
SELECT AVG(COALESCE(marks,0)) FROM sample GROUP BY(name);
You can do this instead:
SELECT SUM(marks) / COUNT(name)
FROM sample
GROUP BY name;
This is the correct behavior, because NULL
is not the same as the number 0
.
This might surprise some non-english speakers, because in many languages "null" is equivalent to "zero".
In SQL, NULL
is not the same as 0
.
Conceptually, NULL
refers to an “unknown value” and as such it is treated differently from other values. That is why aggregate functions like AVG()
ignore NULL
s.
AVG()
calculates the average over all "known" values only. (= that are not NULL)
From the MySQL docs:
Unless otherwise stated, group functions ignore NULL values.
Also, read about the concept of NULL
s in Section "3.3.4.6 Working with NULL Values" of the MySQL manual.
To get what you want, you might do
SELECT AVG(COALESCE(marks, 0))
FROM sample
GROUP BY name;
COALESCE()
returns the next argument for calculations if the value is NULL
or passes through the value otherwise.
There are more common misunderstandings regarding the concept of NULL
. These are also explained in Section "5.5.3 Problems with NULL" of the manual:
- In SQL, the
NULL
value is never true in comparison to any other value, evenNULL
. An expression that containsNULL
always produces aNULL
value unless otherwise indicated in the documentation for the operators and functions involved in the expression.
i.e.:NULL == 0
results in NULL instead oftrue
. AlsoNULL == NULL
results in NULL, instead of true.- To search for column values that are
NULL
, you cannot use anexpr = NULL
test. To look forNULL
values, you must use theIS NULL
test.- When using
DISTINCT
,GROUP BY
, orORDER BY
, allNULL
values are regarded as equal.- When using
ORDER BY
,NULL
values are presented first, or last if you specifyDESC
to sort in descending order.- For some data types, MySQL handles NULL values specially. If you insert
NULL
into aTIMESTAMP
column, the current date and time is inserted.- If you insert
NULL
into an integer or floating-point column that has theAUTO_INCREMENT
attribute, the next number in the sequence is inserted.- A column that has a
UNIQUE
key defined can still contain multipleNULL
values.
Try:
select avg(case marks when null then 0 else marks end) from sample group by name;
Or try and avoid nulls in the table ;)