Why does NVL always evaluate 2nd parameter

Question

Does anyone know, why Oracle\'s NVL (and NVL2) function always evaluate the second parameter, even if the first parameter is not NULL?

Answer 1

It's always been that way, so Oracle has to keep it that way to remain backwards compatible.

Use COALESCE instead to get the short-circuit behaviour.