DevArt的的dotConnect甲骨文VS的DataDirect的ADO.NET数据提供程序 [英] DevArt's dotConnect for Oracle vs DataDirect's ADO.NET data provider
问题描述
有没有人做过的dotConnect的比较分析，甲骨文从DevArt和的> ADO.NET数据提供程序。
Has anybody done a comparative analysis of dotConnect for Oracle from DevArt and the ADO.NET data provider from DataDirect.
我们正在考虑使用实体框架支持，这些框架的关键企业应用程序提供的。我建议阅读以下一些文章：
We are thinking of using the Entity Framework support available in these frameworks for a critical enterprise application. Some articles that I read suggest the following:
- DevArt的dotConnect快得多比的DataDirect
- DataDirect的许可证是比较昂贵的DevArt许可证
任何人都可以扔在技术方面更多的光线，从而帮助决策过程？
推荐答案
由于没有人从无私的当事人没有留下任何评论，我们会尝试后的中性评论越好。
Devart具有较长的EF支持的历史 - 自8月30日，2007年。在这两年里，我们已经考虑到众多的bug报告和用户请求。我们还创建并附带产品的实体开发 - 一个强大的设计时间的工具。
我们不能要求甲骨文我们的实体框架支持的一个理想的 - 这个ORM最初设计用于MS SQL Server的，因此，能考虑到其他DBMS的奇迹是显著有限。
这足以只提CROSS APPLY和OUTER APPLY 问题。
然而，尽管有这些问题，我们的大多数用户都能够与实体框架顺利，舒适的工作。
这将是足够的说，但你所提到的关键企业allpications。
在这种情况下，我们建议您看看我们的Oracle特定的LINQ to SQL实现 - LINQ到Oracle 。
LINQ to SQL不pretend构建跨数据库解决方案，从而使地考虑到一个单独的数据库管理系统，甲骨文特别考虑的特殊性。不同于实体框架，在那里我们有在生成的SQL查询仅部分控制，在LINQ到Oracle情况下，我们拥有完全控制权的过程。这一事实给了我们一个机会，去创造快速和有效的Oracle特定的查询，也加快了bug修复和改进的过程。
如果传统的Oracle数据库EF通常是难以应用，不像LINQ到Oracle。
也进行使用实体开发与LINQ设计时工作到Oracle模型。
As nobody from disinterested parties haven't left any comments yet, we'll try to post as neutral comment as possible.
Devart has longer EF support history - since Aug 30th, 2007. During these two years we have taken into account numerous bug reports and user requests. We also have created and ship with our products Entity Developer - a powerful design time tool.
We cannot call our Entity Framework support for Oracle an ideal one - this ORM was initially designed for MS SQL Server, so the possibility to take into account the marvels of other DBMSs is significantly limited.
It is enough to mention only the CROSS APPLY and OUTER APPLY problem.
But, in spite of these problems, most of our users are capable of working with Entity Framework successfully and comfortably.
That will be sufficient to say, but you have mentioned "critical enterprise allpications".
In this case we recommend you to take a look at our Oracle-specific LINQ to SQL implementation - LINQ to Oracle.
LINQ to SQL does not pretend to build cross-database solutions and hence allows to take into consideration peculiarities of a separate DBMS, Oracle in particular. Unlike Entity Framework, where we have only partial control over the generated SQL queries, in the LINQ to Oracle case we have full control over the process. This fact gives us an opportunity to generate fast and valid Oracle-specific queries and also speeds up bug fixing and improvement process.
In case of legacy Oracle databases EF usually is hard to apply, unlike LINQ to Oracle.
Design time work with LINQ to Oracle model is also performed using Entity Developer.
这篇关于DevArt的的dotConnect甲骨文VS的DataDirect的ADO.NET数据提供程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
