|
|
Don't Bypass the DBA with LINQ, but LINQ Has Its Usefulness I have chosen not to use it to access databases unless the developer calls a stored procedure. Otherwise, LINQ, to me, is like the VB4 bad practice of imbedded and concatenated SQL strings, and, mainly, it bypasses the oversight of the DBA. A DBA in most .NET development shops should approve all stored procedures, and if they are imbedded in application code, how can he or she? Microsoft evangelists tout the one advantage to programmers that they don't have to learn SQL - so why not pass the responsibility to the DBA? Very few experienced programmers are not familiar with SQL, and if Data Store standards for SQL exist in a development environment, why not follow them to write good stored procedure code?
I use it to iterate through objects like a collection of client objects or a generic list. I also use LINQ to access a database if used with a stored procedure. This is the preferred method for accessing XML in lieu of XPATH and XQUERY. This is a great use of LINQ since learning LINQ is not so tedious as mastering XPATH and XQUERY. |
|