Comments on: IQueryable<T> vs. IEnumerable<T> in LINQ to SQL queries http://jonkruger.com/blog/2007/10/19/iqueryable-vs-ienumerable-in-linq-to-sql-queries/ Works on my machine Thu, 04 Dec 2008 00:47:45 +0000 http://wordpress.org/?v=2.1 By: Matt Casto http://jonkruger.com/blog/2007/10/19/iqueryable-vs-ienumerable-in-linq-to-sql-queries/#comment-2215 Matt Casto Sat, 20 Oct 2007 11:37:30 +0000 http://jonkruger.com/blog/2007/10/19/iqueryable-vs-ienumerable-in-linq-to-sql-queries/#comment-2215 I wonder what the result would be if you did something like: var list = dc.Products.Where(p => p.ProductName.StartsWith("A")); I'm not near any computers with Visual Studio installed on them this weekend, so I'll have to wait until next week to try it out. I wonder what the result would be if you did something like:

var list = dc.Products.Where(p => p.ProductName.StartsWith(”A”));

I’m not near any computers with Visual Studio installed on them this weekend, so I’ll have to wait until next week to try it out.

]]> By: Jon http://jonkruger.com/blog/2007/10/19/iqueryable-vs-ienumerable-in-linq-to-sql-queries/#comment-2219 Jon Sat, 20 Oct 2007 17:00:15 +0000 http://jonkruger.com/blog/2007/10/19/iqueryable-vs-ienumerable-in-linq-to-sql-queries/#comment-2219 I tried it and it worked (I got the "TOP 10"). I tried it and it worked (I got the “TOP 10″).

]]> By: WebGyver http://jonkruger.com/blog/2007/10/19/iqueryable-vs-ienumerable-in-linq-to-sql-queries/#comment-2814 WebGyver Thu, 20 Dec 2007 18:00:41 +0000 http://jonkruger.com/blog/2007/10/19/iqueryable-vs-ienumerable-in-linq-to-sql-queries/#comment-2814 Wow! Awesome stuff. I'm nowhere near the level you guys are on, of course, but I have learned a lot from reading through & working through your examples. However, I was wondering if you could enlighten me a little bit about the problems that I would encounter with LINQ (at this point in time) as far as working with SQL Server? To be more specific, I'm faced with rewriting a legacy application, and we've done a ton of development with Stored Procedures in the past. Is LINQ really going to make my life easier (in 2008)? What are the most obvious problems — if any — that I would have to deal with? Links? Ideas? Suggestions? Wow! Awesome stuff. I’m nowhere near the level you guys are on, of course, but I have learned a lot from reading through & working through your examples.

However, I was wondering if you could enlighten me a little bit about the problems that I would encounter with LINQ (at this point in time) as far as working with SQL Server?

To be more specific, I’m faced with rewriting a legacy application, and we’ve done a ton of development with Stored Procedures in the past. Is LINQ really going to make my life easier (in 2008)?

What are the most obvious problems — if any — that I would have to deal with? Links? Ideas? Suggestions?

]]> By: Jon Kruger http://jonkruger.com/blog/2007/10/19/iqueryable-vs-ienumerable-in-linq-to-sql-queries/#comment-2815 Jon Kruger Fri, 21 Dec 2007 02:45:35 +0000 http://jonkruger.com/blog/2007/10/19/iqueryable-vs-ienumerable-in-linq-to-sql-queries/#comment-2815 WebGyver- I'm in a similar situation as you in that I was rewriting a legacy application. I have been very impressed with LINQ to SQL and I would highly recommend it. We are working with a legacy database (SQL Server 2005) that has some really unusual stuff in it, and LINQ to SQL has been able to handle it all. IMO, if you want to get all of the benefits out of LINQ to SQL (or any ORM for that matter), I would try and get away from the stored procedures and allow LINQ to SQL to handle all the work. LINQ to SQL will optimize all of the queries for you, and if you do have a situation where you need to use stored procs, LINQ to SQL can wrap those nicely for you so that calling the stored proc is as easy as calling a method. Good luck! Jon WebGyver-

I’m in a similar situation as you in that I was rewriting a legacy application. I have been very impressed with LINQ to SQL and I would highly recommend it. We are working with a legacy database (SQL Server 2005) that has some really unusual stuff in it, and LINQ to SQL has been able to handle it all.

IMO, if you want to get all of the benefits out of LINQ to SQL (or any ORM for that matter), I would try and get away from the stored procedures and allow LINQ to SQL to handle all the work. LINQ to SQL will optimize all of the queries for you, and if you do have a situation where you need to use stored procs, LINQ to SQL can wrap those nicely for you so that calling the stored proc is as easy as calling a method.

Good luck!

Jon

]]> By: IEnumerable vs IQuerable « Paris Polyzo’s Weblog http://jonkruger.com/blog/2007/10/19/iqueryable-vs-ienumerable-in-linq-to-sql-queries/#comment-3117 IEnumerable vs IQuerable « Paris Polyzo’s Weblog Tue, 18 Nov 2008 13:09:39 +0000 http://jonkruger.com/blog/2007/10/19/iqueryable-vs-ienumerable-in-linq-to-sql-queries/#comment-3117 [...] IEnumerable vs IQuerable Watch the following article:IEnumerable<T> vs IQueryable<T> [...] […] IEnumerable vs IQuerable Watch the following article:IEnumerable<T> vs IQueryable<T> […]

]]>