Come to think of it, there's an inconsistency in the SQL treatment. If you select MAX from a column that contains nulls, the nulls are ignored and you get the highest non-null value.

But according to above logic, you should get NULL - because you can't know if one of the unknown values may be higher than the current maximum.