We have problems when calling stored procedures with parameter values set to null (with OracleMS driver): the parameter is considered to be missing... I found in MSDN that a System.DBNull should be used instead.
When you send a null parameter value to the server, you must specify DBNull, not null. A null value in the system is an empty object that has no value. DBNull is used to represent null values.
...and it works fine if we set the value to DBNull within the generated code.
So would'nt it be right to change the stored procedure generation templates by adding a test on the value passed to the method: if that value is null, then add the parameter with a DBNull value, else keep the code as is?
