Optional Stored Procedure Parameters breaks iBatis code

[Nabours, Mark A.]

We recently had a portion of our iBatis code broken when the author of
MS SQL Server stored procedure added 3 optional parameters.  We had
assumed that iBatis.net would handle this more gracefully.  What is the
recommended way for dealing with this?  Do you have to specify all of
the parameters even though some of them are optional?  

 

If you do that, will your code break again if the maintainer of the
client's stored procedure removes those optional parameters in the
future?  We are currently using version 1.6.1 of IBatisNet.DataMapper.

 

Thanks,

Mark