Comments on: LINQ to SQL & Entity Framework Pitfalls http://www.ytechie.com/2009/09/linq-to-sql-entity-framework-pitfalls.html Productive software development using ASP.NET, C#, Adobe Flex, and other technologies and tools. Thu, 09 Sep 2010 10:53:34 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: corey coogan http://www.ytechie.com/2009/09/linq-to-sql-entity-framework-pitfalls.html/comment-page-1#comment-1611 corey coogan Fri, 02 Oct 2009 13:18:12 +0000 http://www.ytechie.com/2009/09/linq-to-sql-entity-framework-pitfalls.html#comment-1611 No HTML encoding... <property name="hibernate.adonet.batch_size">25</property> No HTML encoding…

<property name=”hibernate.adonet.batch_size”>25</property>

]]> By: corey coogan http://www.ytechie.com/2009/09/linq-to-sql-entity-framework-pitfalls.html/comment-page-1#comment-1610 corey coogan Fri, 02 Oct 2009 13:17:12 +0000 http://www.ytechie.com/2009/09/linq-to-sql-entity-framework-pitfalls.html#comment-1610 Batch updates are in NH and configured through a property. 25 Batch updates are in NH and configured through a property.

25

]]> By: Bart Czernicki http://www.ytechie.com/2009/09/linq-to-sql-entity-framework-pitfalls.html/comment-page-1#comment-1609 Bart Czernicki Fri, 02 Oct 2009 01:31:36 +0000 http://www.ytechie.com/2009/09/linq-to-sql-entity-framework-pitfalls.html#comment-1609 An alternative approach is to use the Linq2Sql/EF to simply retrieve the relevant objects and perform the aggregation/nesting/pivoting in memory on the data objects. I found this approach to be over 10x faster in data-read scenarios. This eliminates the "nasty sql" that you speak of. @Corey, NH has its own set of issues and some performance problems that are still being worked out. I believe that batch updates are still not supported (?) An alternative approach is to use the Linq2Sql/EF to simply retrieve the relevant objects and perform the aggregation/nesting/pivoting in memory on the data objects. I found this approach to be over 10x faster in data-read scenarios.

This eliminates the “nasty sql” that you speak of.

@Corey,

NH has its own set of issues and some performance problems that are still being worked out. I believe that batch updates are still not supported (?)

]]> By: corey coogan http://www.ytechie.com/2009/09/linq-to-sql-entity-framework-pitfalls.html/comment-page-1#comment-1608 corey coogan Thu, 01 Oct 2009 19:28:19 +0000 http://www.ytechie.com/2009/09/linq-to-sql-entity-framework-pitfalls.html#comment-1608 Nice post Jason. I stay away from Linq to SQL and EF like the plague but have been using Linq to NH and other providers. You've helped remind me to keep these things in mind, especially after seeing the exception you got with the 1==2 clause. I would have expected to at least see 0 if not null. Nice post Jason. I stay away from Linq to SQL and EF like the plague but have been using Linq to NH and other providers. You’ve helped remind me to keep these things in mind, especially after seeing the exception you got with the 1==2 clause. I would have expected to at least see 0 if not null.

]]>