blocks|key|1803757|text|好的--这就是skinny：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1803758|该特定视图被设置为存储过程的返回类型，该存储过程必须在模型的实体容器中设置为函数导入。|1803759|我已经更新了该视图以适应新的报告需求，但没有意识到它对函数导入的重要性。附加字段不是为此目的识别的数据集的一部分，因此它找不到与它们中的任何一个匹配的字段。|1803760|所以我复制了这个视图，并给它添加了'Report‘后缀，然后将原始视图还原为它期望的一组返回字段。|1803761|瞧！|1803762|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Ok - here's the skinny:

That particular view was setup as a Return Type for a Stored Procedure that had to be setup as a Function Import in the Model's Entity Container.

I had updated that view to fit new reporting requirements, not realizing it's significance to the Function Import. The additional fields are not part of the data set recognized for this purpose, so it couldn't find a match for any of them.

So I duplicated the view and suffixed it with 'Report', then reverted the original back to it's expected set of return fields.

Voila!

blocks|key|2365954|text|除了更新视图之外，您还可以更新函数Import：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2365955|转到模型浏览器窗口，展开映射详细信息窗口中的EntityContainer|2365956|Open+|unordered-list-item|2365957|函数|2365958|如果实体名称(左列)与预期的字段名称(右列)不匹配，则可以更改右列以匹配返回字段的实际调用。|2365959|2365960|2365961|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|R|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|S|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

Rather than updating the view, you can also update the Function Import:

<ul>
<li>Go to the Model Browser window</li>
<li>Expand the EntityContainer</li>
<li>Open the Function Import in the Mapping Details window</li>
<li>If the entity name (left column) does not match the expected field name (right column), you can change the right-hand column to match what the returned field is actually called.</li>
</ul>

blocks|key|5894219|text|我遇到了一个类似的问题，它产生了相同的错误消息--问题是proc返回的列名包含一个空格。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5894220|在创建复杂类型时，[my+column]被创建为my_column。|offset|length|style|CODE|5894221|然后，当使用ExecuteStoreQuery执行proc时，数据读取器中不存在my_column，因为proc仍然返回[my+column]。|5894222|解决方案:删除proc列名中的空格，并为导入的函数重新创建复杂类型。|5894223|entityMap^0|0|9|B|O|9|0|6|H|14|9|1O|B|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]|$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@$D|U|E|V|F|G]|$D|W|E|X|F|G]|$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$]]

I had a similar issue which produced the same error message - the problem was that a column name returned by the proc included a space.

When creating the complex type, <code>[my column]</code> was created as <code>my_column</code>.

Then when executing the proc with <code>ExecuteStoreQuery</code>, <code>my_column</code> did not exist in the data reader, as the proc still returned <code>[my column]</code>.

Solution: remove the space from proc column name and recreate your complex type for the imported function.

blocks|key|2366049|text|我最近在使用Sprocs时遇到了同样的问题。我在存储过程中使用了几个'if‘语句作为条件SQL|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2366050|IF+@param1+=+'knownValue'
BEGIN
SELECT+*+FROM+EntityType+WHERE+ID+=+'somevalue'
END
ELSE+IF+@param1+=+'knownValue2'
BEGIN
SELECT+*+FROM+EntityType+WHERE+ID+=+'somevalue'
END|code-block|syntax|javascript|2366051|下面是我的EF代码：|2366052|return+context.Database.SqlQuery<EntityType>(
++++++++++++"[NAV].[GeEntityType]+@Date,+@ID",
++++++++++++new+SqlParameter("Date",+paramDate),
++++++++++++new+SqlParameter("ID",+paramId)).ToList();|2366053|我没有考虑到'if‘语句都没有返回true的情况，所以sproc甚至没有返回一个空的结果集，并导致EF抛出这个错误。在没有返回空的读取器的情况下，EF在将列映射到属性时没有匹配的内容。|2366054|希望能有所帮助。|2366055|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I came up against the same issue when using Sprocs recently. I had some conditonal SQL in the sproc along the lines of a couple of 'if' statements

<pre><code>IF @param1 = 'knownValue'
BEGIN
SELECT * FROM EntityType WHERE ID = 'somevalue'
END
ELSE IF @param1 = 'knownValue2'
BEGIN
SELECT * FROM EntityType WHERE ID = 'somevalue'
END
</code></pre>

here's my EF code:

<pre><code>return context.Database.SqlQuery&lt;EntityType&gt;(
 "[NAV].[GeEntityType] @Date, @ID",
 new SqlParameter("Date", paramDate),
 new SqlParameter("ID", paramId)).ToList();
</code></pre>

I had not catered for scenarios where neither 'if' statements returned true, so the sproc wasn't even returning an empty resultset and caused EF to throw this error. Without returning even an empty reader, EF had nothing to match when mapping columns to properties.

Hope it helps.

blocks|key|5894385|text|我曾在改变结果集的数据对象上看到过这种情况(例如，带有if语句的存储过程)，错误消息是实体框架/数据读取器，它告诉您它需要列x，但没有返回。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5894386|要解决这个问题，您可以a)确保存储过程的所有路径都返回相同的列名b)使用Database.ExecuteSqlCommand|5894387|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Ive seen this happen on data objects that vary the result set (for example a sproc with an if statement) The error message is Entity Frame work/ Data reader telling you that it expected column x and it wasn't returned.

To work around this you can either
a) Make sure all paths of your sproc return the same column names
b) Use Database.ExecuteSqlCommand

blocks|key|4478713|text|简单的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4478714|4478715|+SP完成后，更新EF模型以使其可用。|ordered-list-item|4478716|将打印语句添加到SP，重新编译并运行。|4478717|注释掉动态SQL并放入打印语句，重新编译以确保其运行。|4478718|现在在EF中执行函数导入，将显示列。|4478719|将SP更改回动态代码，一切正常：)<代码>H210<代码>G211|4478720|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

Easy Way:

<ol>
<li>Once SP is complete update EF Model so it is available.</li>
<li>Add PRINT statement to SP, re-compile and run.</li>
<li>Comment out Dynamic SQL and put in PRINT statement, recompile ensure it runs.</li>
<li>Now do Function Import in EF, columns will show.</li>
<li>Change SP back to Dynamic code and all good :)</li>
</ol>

Using VS 2008, SQL Server 2008 and WPF 3.5, I've made some changes to my schema and updated the model. It compiles and runs fine, until the client app calls for a specific entity and I get the following (actual names replaced):

<pre><code>The data reader is incompatible with the specified '&lt;Model&gt;.&lt;ViewBasedEntity&gt;'. A member of the type, '&lt;Property&gt;', does not have a corresponding column in the data reader with the same name.
</code></pre>

I've searched through the services app for related entity and property names, tried renaming properties in the Table Map, Seems to be a number of others out there reporting the same error, but can't seem to find a timely answer....

...Does anyone know how to track this down, and if so, is there a fix or methodology to follow to avoid in the future?

Data reader is incompatible... member does not have corresponding column in data reader

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

使用VS2008、SQL Server2008和WPF3.5，我对我的模式进行了一些更改，并更新了模型。它可以很好地编译和运行，直到客户端应用程序调用了一个特定的实体，并且我得到了以下内容(实际名称被替换)：The data reader is incompatible with the specified '<Mod...

问数据读取器不兼容...成员在数据读取器中没有对应的列
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问数据读取器不兼容...成员在数据读取器中没有对应的列EN