Depend on how you use it. I find that it works great. I defined my class properties as nullable generic and map it as stored procedure parameters.
Another thing I like about being able to do dynamic SQL is that I can call the stored procedure from dynamic SQL. Example: <select ...> EXEC dbo.up_GetSomeValue #value# </select> It's not actually dynamic because I found during SQL Profiling that Ibatis convert this statement into: sql_execute 'EXEC dbo.up_GetSomeValue @param1', @param1 = N'blah blah' Regards, Tom Nguyen Sr. Developer [EMAIL PROTECTED] Rels Valuation -----Original Message----- From: Garth Keesler [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 14, 2007 5:22 AM To: [email protected] Subject: Re: default parameter mapping for stored procedures I agree. My experience with iBatisNet is that the support for stored procedures isn't quite as "robust" as the counterpart in iBatis Java. I finally quit trying to use that particular feature and instead code the calls directly in c# functions. Not great but workable, Garth Gilles Bayon wrote: > iBATIS doesn't support it. > > -- > Cheers, > Gilles ************************************************************************************ This e-mail message and any files transmitted herewith, are intended solely for the use of the individual(s) addressed and may contain confidential, proprietary or privileged information. If you are not the addressee indicated in this message (or responsible for delivery of this message to such person) you may not review, use, disclose or distribute this message or any files transmitted herewith. If you receive this message in error, please contact the sender by reply e-mail and delete this message and all copies of it from your system. ************************************************************************************
