Null values in procedure input parameters
I have a debate with the application developers (c#)
They claim that it is malpractive of passing NULL values into procedure. Instead, they want me to handle it as:
Such as adding 1 "true/false" field to your procedure inputs:
Where input_number = database_value OR input_number is null
Where input_number = database_value OR ( ignore_input_number_flag = true )
What is the best way to handle NULL values?