June 18, 2009 at 9:54 pm
Comments posted to this topic are about the item LINQ - SQL Server 2008
June 19, 2009 at 5:53 am
According to the definition it should be Language INtegrated Query, with a capital N also...
June 19, 2009 at 7:48 am
Is there anyone who actually uses LINQ? I'm jut curious because to me conceptually it seems to just add an extra layer of complexity to an already over complex model to begin with in the .Net world. I guess I've never understood why people are so afraid of databases that they feel the need to pretend they don't even exist and build up all sorts of abstract persistance models to avoid them. I've also always been a fan of the line of thought that you should put the processing where it makes sense, so data logic belongs in the database, user interface logic belongs in the top layer, etc. Or maybe I'm just too old fasioned and don't get you youngins 😉
June 19, 2009 at 8:45 am
The short answer is yes. LINQ can do much more than just query Sql Server. It is also one way to deal with Object / Relational dataase impedence.
June 19, 2009 at 10:15 am
There are lots of developers trying to use LINQ, though not necessarily just to SQL Server. You can use to to get to XML, and other data sources.
June 21, 2009 at 8:04 am
I guess I'll never get it then. To me, XML is only a transfer mechanism of hierarchical data between potentially heterogeneous systems, not a place to persist data. It also doesn't make sense to me to want to query an object in .Net. An object should only have the data you need at that time to do the function you're trying to do. That's an example of someone trying to do database logic in an application layer, and in the long run can only cause more problems than it solves.
As developers, we have lots of tools in our toolbox, but it is our responsibility to know what the purpose of those tools are, and when is the proper time to use each tool. The problem is, the companies like Microsoft are more interested in selling us newer and newer versions of their products, and have new features just for the sake of having new features. It's similar to the Object Oriented Database discussion that went on here earlier this week. OODBs haven't caught on much because they are a solution looking for a problem. LINQ to me is also a solution looking for a problem. If there was an existing problem that LINQ was trying to solve, then it would have caught on more by now, and Microsoft wouldn't be trying to take it out of the limelight.
June 22, 2009 at 6:39 am
Chris Harshman (6/21/2009)
LINQ to me is also a solution looking for a problem.
Chris,
I think that's the best description of LINQ to SQL I have ever heard! 😛
As a SQL DBA, I don't see the need for it, or any other abstraction, but I guess in smaller companies where there is no DBA , or even seasoned database pro, it gets quite a lot of leverage from the app developers.
But I don't want to start a war, so rant over before it begins!
Just see it as potential opportunities a few years done the line - companies will need SQL 'experts' to performance tune their apps - we can step in, move the code into SPs, claim the glory and move onto the next one!
Kev
December 11, 2009 at 4:03 am
The answer was bit easy one - but i have never used LINQ.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply