On Thu, 07 Jun 2012 06:47:05 +0100, Mehrdad <[email protected]> wrote:
On Thursday, 7 June 2012 at 05:09:27 UTC, Alex Rønne Petersen wrote:
On 07-06-2012 07:04, Mehrdad wrote:
no programming language will save you from that
LINQ isn't exactly susceptible to SQL injection. :P
LINQ can't mutate the state of the DB, only query it. LINQ far from
covers everything.
True enough, although it's not too difficult to imagine an extension of
LINQ where that is indeed possible.
Nonetheless, the following /is/ called "LINQ to SQL" (why, I don't know):
http://msdn.microsoft.com/en-us/library/bb386941.aspx
I've done some work with LINQ to SQL recently. The reason that is labeled
as such is that the DataContext object which is used in those examples is
one generated by the LINQ architecture from a SQL database. So, while
this has nothing to do with LINQ style statements in code, it is related
to the objects those statements are used on/with. :)
R
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
