Prev: Sql Server on VMWare
Next: AdventureWorks database
From: Michael C on 8 Dec 2009 19:49 "Michael Coles" <admin(a)geocodenet.com> wrote in message news:%23q64heGeKHA.2164(a)TK2MSFTNGP02.phx.gbl... > Since we're really stretching the definition of "support for TVPs", we can > surely stretch the definition of "support for digestion" to include the > Food Network. As you say, it depends on how you look at it, if you choose > to look at it that way. :) The fact that the LINQ providers have no > support for TVPs is not even a question. The fact that you can kludge > around the lack of support by adding a layer of abstraction between SQL > Server and LINQ doesn't change that fact. > > We could likewise say that JavaScript has no support for querying SQL > Server directly; however, we can put a Web Service in between JavaScript > and SQL Server to accept requests from JavaScript, connect to SQL Server, > execute the query, and return the results to JavaScript in JSON format. > This doesn't mean JavaScript now suddenly *poof* supports SQL Server > querying -- what it means is we have added a layer of abstraction in > between JavaScript and SQL Server that can communicate with both. You've > proposed the same thing with ADO.NET, which doesn't suddenly mean that > *wow* LINQ suddenly supports TVPs. Looks like we're going to have to agree to disagree on this extremely minor, drawn out point. Michael |