The SqlParameter is already contained by another SqlParameterCollection.

最新推荐文章于 2022-05-25 22:02:07 发布

weixin_30525825

最新推荐文章于 2022-05-25 22:02:07 发布

阅读量71

点赞数

CC 4.0 BY-SA版权

文章标签：数据库

原文链接：http://www.cnblogs.com/ywqu/archive/2009/02/22/1396004.html

在调试一个概念验证应用时，遇到使用同一组SQL参数执行不同SqlCommand对象导致的SqlParameter已由另一个SqlParameterCollection包含异常。通过在执行后清理SqlCommand参数解决了此问题。

以下是从国外网站找到的解决办法

Yesterday, I came across a odd bug while debugging some code for a proof of concept application.

The code itself was simple connecting to the database, executing two queries using different SqlCommand objects, but the same SqlParameter collection and returning the results to the user.

The method itself look two parameters, a SQL query as a string and a SQL Parameter[]. I would then simply add the parameters to the SqlCommand:

SqlCommand sqlCmd = new SqlCommand(sql, sqlConn);
sqlCmd.Parameters.AddRange(queryParams);

After executing I would close the connection, then code would do some other stuff and a different query would be executed but using the same parameter collection. In theory, there is no reason why this wouldn't work however the code was throwing an exception with the error "The SqlParameter is already contained by another SqlParameterCollection." How odd, I had closed the connection and it shouldn't be referred so I should be able to add it.

Turns out, or at least I think, that the garage collection isn't kicking in quick enough and so the reference is still alive. Quick fix was to clear the parameters on the SqlCommand object after execution.

sqlCmd.Parameters.Clear();

Tripped me up for a little bit so I thought I would post. Carry on...

转载于:https://www.cnblogs.com/ywqu/archive/2009/02/22/1396004.html