<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://forums.asp.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Search results matching tag 'ThinqLinq'</title><link>http://forums.asp.net/search/SearchResults.aspx?q=&amp;tag=ThinqLinq&amp;orTags=0&amp;o=DateDescending</link><description>Search results matching tag 'ThinqLinq'</description><dc:language>en-US</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>Re: To LINQ, Or Not To LINQ etc.</title><link>http://forums.asp.net/thread/2189757.aspx</link><pubDate>Fri, 22 Feb 2008 05:00:00 GMT</pubDate><guid isPermaLink="false">4c671506-2930-414c-a40b-8bf57ded5924:2189757</guid><dc:creator>jwooley</dc:creator><description>&lt;p&gt;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).&lt;/p&gt;
&lt;p&gt;I&amp;#39;m sorry we didn&amp;#39;t get a chance to chat at the Raleigh code camp last weekend. Come on over to &lt;a href="http://www.thinqlinq.com/"&gt;www.ThinqLinq.com&lt;/a&gt; and check out some of the possibilities that you can do with LINQ. Better yet, check out my new book, &lt;a class="" title="LINQ in Action" href="http://www.manning.com/affiliate/idevaffiliate.php?id=263_74"&gt;LINQ in Action&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Jim&lt;/p&gt;</description></item></channel></rss>