根据这篇文章： https://connect.microsoft.com/VisualStudio/feedback/details/362523/sqlmetal-error-when-used-on-a-database-with-a-table-valued-parameter#tabs< /a>
和我发现的其他几篇文章包含 4.0 中 LINQ to Sql 的功能和错误修复列表，这应该是修复的，因为它会简单地忽略该 Sproc 并继续它的快乐 方式。
SQL 金属
<块引用>
- 外键属性设置器现在检查所有受影响的关联，而不仅仅是第一个
- 改进了主键类型不受支持时的错误处理
- 现在会跳过包含表值参数的存储过程，而不是中止进程
- 现在可用于使用 AttachDbFilename 语法的连接
- 遇到意外数据类型时不再崩溃
我已经安装了最新的 SDK (v7.1)，并且 sqlmetal.exe 仍然无法通过该存储过程。
有谁知道是否包括承诺的改进（跳过而不是轰炸）？如果有，是哪个版本？
According to this post: https://connect.microsoft.com/VisualStudio/feedback/details/362523/sqlmetal-error-when-used-on-a-database-with-a-table-valued-parameter#tabs
and several other posts I've found containing a list of features and bug fixes for LINQ to Sql in 4.0 this was supposed to be fixed in that it would simply ignore that Sproc and go on it's merry way.
SQL Metal
- Foreign key property setter now checks all affected associations not just the first
- Improved error handling when primary key type not supported
- Now skips stored procedures containing table-valued parameters instead of aborting process
- Can now be used against connections that use AttachDbFilename syntax
- No longer crashes when unexpected data types are encountered
I have installed the newest SDK (v7.1) and sqlmetal.exe is still not getting past that stored procedure.
Does anyone know if that promised improvement (of skipping instead of bombing) was included? And if so, in which version?
发布评论