Comments on: LINQ-to-Entities: Follow-Up http://www.hackification.com/2008/12/04/linq-to-entities-follow-up/ Fri, 23 Jul 2010 14:53:52 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Demented Devil http://www.hackification.com/2008/12/04/linq-to-entities-follow-up/comment-page-1/#comment-190 Demented Devil Tue, 31 Mar 2009 12:43:43 +0000 http://www.hackification.com/?p=62#comment-190 As someone who was forced to write their own ORM using VS2005 I can say that I love BOTH L2S and EF. Which one do I use? Well that depends. However I can tell you that my ORM stole the EntitySet/EntityRef/lazy loading and object caching concepts from EF it worked fantastically well although it was far from perfect and far from painless... If its magic you want then look no further than LINQ - that is the true piece of wonder code. These days I'm having plenty of fun with RIA Services which reuses EF and Silverlight! Besides which - nobody says you HAVE to use it - you don't like it - fine - stop bitching! As someone who was forced to write their own ORM using VS2005 I can say that I love BOTH L2S and EF. Which one do I use? Well that depends. However I can tell you that my ORM stole the EntitySet/EntityRef/lazy loading and object caching concepts from EF it worked fantastically well although it was far from perfect and far from painless…

If its magic you want then look no further than LINQ – that is the true piece of wonder code.

These days I’m having plenty of fun with RIA Services which reuses EF and Silverlight!

Besides which – nobody says you HAVE to use it – you don’t like it – fine – stop bitching!

]]> By: J.C http://www.hackification.com/2008/12/04/linq-to-entities-follow-up/comment-page-1/#comment-189 J.C Wed, 21 Jan 2009 10:41:06 +0000 http://www.hackification.com/?p=62#comment-189 In you example, if I needed the header and the answers and so forth I would use the "Includes" method on a L2E for each of the related data you need. See this article for an example: http://blogs.msdn.com/bethmassi/archive/2008/12/10/master-details-with-entity-framework-explicit-load.aspx EF has many ways to access data. You can use L2E, eSQL or even EntityClient directly. Being able to choose the best option in the context you are working its in my opinion something good, not bad. Being able to load imediatly or only when I really need related data is also important for me. And to anyone that cares about scalability and performance. I'm not saying that EF is perfect. Far from it. It has many shortcommings that propably will be addressed in v2. And thats the point. Its v1 and already has a huge potential. How many products as complex as this may say the same at V1? BTW... I'm using v1 today on production and I'm loving it. Moving from a another similar product to EF will raise issues for sure. People are used to work on a certain way. Thats a good thing because as I see it, Microsoft has will be including a lot of feedback for v2. As for me, I'm amazed by the complexity and reach of V1 as it is. I'm expecting a V2 full of new stuff. Who knows. You will probably get an propertie that allows you to lazyload stuff. Not that I care about it. Afterall... you can actually change the partial class of the model to do what you need without having to wait for MS to do it. T4 template is the magic word. regards In you example, if I needed the header and the answers and so forth I would use the “Includes” method on a L2E for each of the related data you need.

See this article for an example:
http://blogs.msdn.com/bethmassi/archive/2008/12/10/master-details-with-entity-framework-explicit-load.aspx

EF has many ways to access data. You can use L2E, eSQL or even EntityClient directly. Being able to choose the best option in the context you are working its in my opinion something good, not bad. Being able to load imediatly or only when I really need related data is also important for me. And to anyone that cares about scalability and performance.

I’m not saying that EF is perfect. Far from it. It has many shortcommings that propably will be addressed in v2. And thats the point. Its v1 and already has a huge potential. How many products as complex as this may say the same at V1?

BTW… I’m using v1 today on production and I’m loving it. Moving from a another similar product to EF will raise issues for sure. People are used to work on a certain way. Thats a good thing because as I see it, Microsoft has will be including a lot of feedback for v2.

As for me, I’m amazed by the complexity and reach of V1 as it is. I’m expecting a V2 full of new stuff. Who knows. You will probably get an propertie that allows you to lazyload stuff. Not that I care about it. Afterall… you can actually change the partial class of the model to do what you need without having to wait for MS to do it. T4 template is the magic word.

regards

]]> By: George Mavritsakis http://www.hackification.com/2008/12/04/linq-to-entities-follow-up/comment-page-1/#comment-188 George Mavritsakis Mon, 22 Dec 2008 13:41:20 +0000 http://www.hackification.com/?p=62#comment-188 Perfect article, I couldn't agree you you more! But, then, what is the solution? Use Linq-to-SQl or write plain sql? Can Linq-to-sql replace the sql queries and actually help you? Or ... say ... maybe ... nHibernate? Thanks! Perfect article,
I couldn’t agree you you more!
But, then, what is the solution? Use Linq-to-SQl or write plain sql?
Can Linq-to-sql replace the sql queries and actually help you?
Or … say … maybe … nHibernate?

Thanks!

]]> By: Brad http://www.hackification.com/2008/12/04/linq-to-entities-follow-up/comment-page-1/#comment-187 Brad Thu, 11 Dec 2008 15:38:01 +0000 http://www.hackification.com/?p=62#comment-187 I like my LINQ-to-SQL magic thank you very much. You can't have it! I like my LINQ-to-SQL magic thank you very much. You can’t have it!

]]> By: Kristofer http://www.hackification.com/2008/12/04/linq-to-entities-follow-up/comment-page-1/#comment-186 Kristofer Wed, 10 Dec 2008 03:30:38 +0000 http://www.hackification.com/?p=62#comment-186 Excellent summary of the EF shortcomings on the 'coding side' of things. Add to that what comes out on the 'other side', e.g. the poor SQL generated by Linq-to-Entities vs the highly optimized and efficient SQL generated by Linq-to-SQL. The MSDN forum for EF has a lot of horror stories and examples where simple 5-table joins come out as 1500+ table SQL queries. Excellent summary of the EF shortcomings on the ‘coding side’ of things.

Add to that what comes out on the ‘other side’, e.g. the poor SQL generated by Linq-to-Entities vs the highly optimized and efficient SQL generated by Linq-to-SQL.

The MSDN forum for EF has a lot of horror stories and examples where simple 5-table joins come out as 1500+ table SQL queries.

]]> By: Moran http://www.hackification.com/2008/12/04/linq-to-entities-follow-up/comment-page-1/#comment-185 Moran Tue, 09 Dec 2008 18:09:13 +0000 http://www.hackification.com/?p=62#comment-185 "LINQ-to-Entities is like LINQ-to-SQL but with the magic removed." Very Good ! Thank you for a lovely article “LINQ-to-Entities is like LINQ-to-SQL but with the magic removed.”

Very Good !
Thank you for a lovely article

]]> By: Chad http://www.hackification.com/2008/12/04/linq-to-entities-follow-up/comment-page-1/#comment-184 Chad Fri, 05 Dec 2008 01:32:09 +0000 http://www.hackification.com/?p=62#comment-184 “LINQ-to-Entities - now with 100% less magic!” lol... “LINQ-to-Entities – now with 100% less magic!”

lol…

]]>