Essentially, we have to make a decision (programmatically) in terms of how to handle null parameter values in regards to stored procedures and specifically in terms of any argument defaults that might be defined on the database. At the moment our support decides to not pass along the null in the desire to not "over power" any defined argument defaults - if we pass the NULL, the database would use that rather than the defined argument default.

Essentially it is one of those 50/50 calls. Maybe its best to have this be configurable? If we go this route, where all does it make sense to allow this to be configured? per-SessionFactory? per-query? per-param? All of the above? Some of the above? If we go this route, I think my preference would be to allow this to be declared "globally" per-SessionFactory and then possibly allow to override (hint) that per-query. I think per-param is overkill.