为什么没有实体框架支持ODBC？ [英] Why doesn't Entity Framework support ODBC?

问题描述

是否有外汇基金需要新的数据提供者和不能利用ODBC的具体原因是什么？我想它必须是一些ORM具体问题，但NHibernate的通过ODBC正常工作。

Is there a specific reason that the EF requires new data providers and can't make use of ODBC? I figured it had to be some ORM specific problem, but NHibernate works fine via ODBC.

我使用NHibernate和可以继续使用NHibernate的，但我担心，我可以不承担任何未来的程序员在这里NHibernate的知识。

I'm using NHibernate and can continue to use Nhibernate, but I worry that I can't assume Nhibernate knowledge for any future programmers here.

推荐答案

实体框架并不需要新的数据提供者，完全吻合。相反，它需要实体框架提供程序，能够扩展现有的数据提供商，为客户提供由实体框架，需要额外的服务，比如复杂的SQL生成，而不是现有的ADO.NET数据模型的一部分​​。我不认为这有什么写入基于现有的ADO.NET 2.0 ODBC桥的实体框架提供了ODBC停止任何人。您也可以下载源$ C ​​$ C为样本SQL Server提供了解究竟哪些服务的更多信息扩展现有的ADO.NET提供的实体框架时必需的。

The Entity Framework doesn't require new data providers, exactly. Rather, it requires Entity Framework providers which extend existing data providers, to provide additional services required by the Entity Framework, such as complex SQL generation, which are not part of the existing ADO.NET data model. I don't think that there's anything stopping anyone from writing an Entity Framework provider for ODBC based on the existing ADO.NET 2.0 ODBC bridge. You can download the source code for a sample SQL Server provider for more information about exactly what services are required when extending an existing ADO.NET provider for the Entity Framework.

这篇关于为什么没有实体框架支持ODBC？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！