Dave, you are correct that LINQ (to SQL) does not support all of the ANSI sql keywords, but it does support enough to cover a large percentage of your data access needs. In cases that it is missing some statements or extremly complex queries, you are still
able to use Stored Procs and call them as simple function calls in your code. It is important to understand that LINQ has nothing to do with databases. The LINQ to SQL provider which sits on top of LINQ is responsible for working with databases (the SQL server
family in particular).
I'm sorry we didn't get a chance to chat at the Raleigh code camp last weekend. Come on over to
www.ThinqLinq.com and check out some of the possibilities that you can do with LINQ. Better yet, check out my new book,
LINQ in Action.
jwooley
Member
55 Points
20 Posts
Re: To LINQ, Or Not To LINQ etc.
Feb 22, 2008 11:55 AM|LINK
Dave, you are correct that LINQ (to SQL) does not support all of the ANSI sql keywords, but it does support enough to cover a large percentage of your data access needs. In cases that it is missing some statements or extremly complex queries, you are still able to use Stored Procs and call them as simple function calls in your code. It is important to understand that LINQ has nothing to do with databases. The LINQ to SQL provider which sits on top of LINQ is responsible for working with databases (the SQL server family in particular).
I'm sorry we didn't get a chance to chat at the Raleigh code camp last weekend. Come on over to www.ThinqLinq.com and check out some of the possibilities that you can do with LINQ. Better yet, check out my new book, LINQ in Action.
Jim
Linq LINQ in Action ThinqLinq
http://www.ThinqLinq.com
http://www.LinqInAction.net