在实体框架的思考 [英] Thoughts on Entity Framework
问题描述
我想知道是什么人想过,支持实体框架在LINQ到SQL的决定?我有我开发最初在LINQ到SQL的应用程序。我发现它对于我们的应用的完美解决方案。
I was wondering what people thought about the decision to support Entity Framework over LINQ-to-SQL? I have an application I'm developing originally in LINQ-to-SQL. I found it the perfect solution for our application.
在尝试移植到实体框架我很惊讶它是如何粗糙了。恕我直言,甚至还没有接近准备好黄金时间。无延迟加载,无波苏斯,在继承可怕的依赖。我发现它在我的情况主要是无法使用的,而是决定坚持使用LINQ到SQL,直到不知何故这个实体框架可以得到更多的打磨。
While attempting to port to Entity Framework I was surprised how rough it was. IMHO, not even close to being ready for prime time. No lazy loading, no POCOs, horrible dependency on inheritance. I found it largely unusable in my case and instead decided to stick with LINQ-to-SQL until somehow this Entity Framework can get more polished.
任何人有与它类似的经历?
Anyone else have similar experience with it?
推荐答案
这是pretty的很多我的看法。见我的previous答复<一href="http://stackoverflow.com/questions/276433/do-you-think-its-advantageous-to-switch-to-entity-framework#276439">here.这另一个问题是没有具体关于EF的问题,但肯定的:它有一个公平的一些小问题。举例来说(除了现有的选项):
That is pretty much my view. See my previous reply here. This other question wasn't specifically about the problems in EF, but yes: it has a fair few glitches. For example (in addition to your existing options):
- 为
防爆pression.Invoke
(重新使用前pression树木,形成一个更复杂的EX pression)李不支持> - 对于表的UDF的支持,它可以被用来创造良好定义的,可调用方法在数据库中仍然是可组合使用排序/跳过/带等
- no support for
Expression.Invoke
(re-using expression trees to form a more complex expression) - no support for table-UDFs, which can be used to create well-defined, callable methods in the database that are still composable with sort/skip/take etc
LINQ到SQL同时处理就好了......
LINQ-to-SQL handles both just fine...
这篇关于在实体框架的思考的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!