Has your opinion of your EF support changed since 2009?

Discussion of open issues, suggestions and bugs regarding Entity Framework support in ADO.NET Data providers
Post Reply
Posts: 17
Joined: Fri 09 Nov 2012 17:52

Has your opinion of your EF support changed since 2009?

Post by cResults » Wed 05 Dec 2012 18:21

In doing research on our Entity Framework queries that don't work against Oracle with dotConnect, I came across this post and was wondering if your opinion of your product has changed since 2009.

Any guidance that you could give on the OUTER APPLY issue would also be appreciated.
As nobody from disinterested parties haven't left any comments yet, [NOTE] 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.

share|improve this answer
answered Nov 26 '09 at 15:19

http://stackoverflow.com/questions/1781 ... a-provider
I'd like to note my opinion. My attempt to run our EF queries with a trial of dotConnect has not been exactly smooth, however, I am finding that most of my ongoing issues are actually with Oracle and not with Devart. The issues that I have had with Devart have been promptly resolved. Thank you.


David C

Site Admin
Posts: 8241
Joined: Thu 14 Aug 2008 12:44

Re: Has your opinion of your EF support changed since 2009?

Post by Shalex » Thu 06 Dec 2012 15:53

Post Reply