Prevent multiexecute on parameters with type IDynamicMetaObjectProvider or IEnumerable<KeyValuePair<string, object>> #151

Activity

1. tl24 commented on Sep 27, 2014

   

   tl24

   on Sep 27, 2014

   More actions

   I'm having the same issue as well
2. mgravell commented on Sep 27, 2014

   

   mgravell

   on Sep 27, 2014

   Member

   More actions

   Yep, that sounds undesirable - possibly a regression; I'll try to deploy an
   update this weekend.
   On 28 Aug 2014 05:59, "Dennis Apter" [email protected] wrote:

   I use ExpandoObject for initialize execute parameters. If take a look at
   SqlMapper.Execute() method, multiExec enables on IEnumeable param, but it's
   unexpected behavior with ExpandoObject. Please, add additional conditions
   like this:

   if (multiExec != null && !(multiExec is string) && !(multiExec is IDynamicMetaObjectProvider) && !(multiExec is IEnumerable<KeyValuePair<string, object>>)){
   // execute as multiExec}

   —
   Reply to this email directly or view it on GitHub
   #151.
3. mgravell commented on Sep 29, 2014

   

   mgravell

   on Sep 29, 2014

   Member

   More actions

   1.35 released - currently not the default, while I dogfood it etc, but is
   available

   On 27 September 2014 10:40, Marc Gravell [email protected] wrote:

   Yep, that sounds undesirable - possibly a regression; I'll try to deploy
   an update this weekend.
   On 28 Aug 2014 05:59, "Dennis Apter" [email protected] wrote:

   I use ExpandoObject for initialize execute parameters. If take a look at
   SqlMapper.Execute() method, multiExec enables on IEnumeable param, but it's
   unexpected behavior with ExpandoObject. Please, add additional conditions
   like this:

   if (multiExec != null && !(multiExec is string) && !(multiExec is IDynamicMetaObjectProvider) && !(multiExec is IEnumerable<KeyValuePair<string, object>>)){
   // execute as multiExec}

   —
   Reply to this email directly or view it on GitHub
   #151.

   Regards,

   Marc
4. mgravell commented on Sep 29, 2014

   

   mgravell

   on Sep 29, 2014

   Member

   More actions

   Now working fine in production stackoverflow.com etc, so released as default NuGet package. I'm assuming this is now closed, unless I hear "that still doesn't work"
5. mgravell

   closed this as completedon Sep 29, 2014