| Author |
Topic |
|
russell
Pyro-ma-ni-yak
5072 Posts |
 Posted - 2012-03-22 : 13:11:00
|
| Any of ya'll have to deal with Linq to SQL?I've successfully fought it off for years, but alas, the war has been lost. Performance can't be far behind.I'm still incredulous that anyone thinks this is a good idea in a large enterprise. |
|
|
DonAtWork
Master Smack Fu Yak Hacker
2167 Posts |
Posted - 2012-03-22 : 13:47:06
|
| Ugh. Visual Studio magazine did a couple features on LINQ. SOMEONE thinks it is good. I h8 it.How to ask: http://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspxFor ultra basic questions, follow these links.http://www.sql-tutorial.net/ http://www.firstsql.com/tutor.htm http://www.w3schools.com/sql/default.asp |
 |
|
|
elwoos
Master Smack Fu Yak Hacker
2052 Posts |
Posted - 2012-03-23 : 10:01:51
|
| I've managed to avoid it (and Javascript too) but I get the feeling it won't last too much longer, LINQ might be useful for some of the things I have coming upsteve-----------If you can't spot the sucker, its you. |
|
|
|
sunitabeck
Master Smack Fu Yak Hacker
5155 Posts |
Posted - 2012-03-23 : 10:24:29
|
| LINQ to Object, LINQ to XML, LINQ to DataSet are all nice - I love the syntax and the compact and intuitive nature of it (lambda expressions etc.). But, LINQ To SQL? Ugh!! I feel like I have very little control over the query it generates, and very little control over how it gets executed (lazy loading? no, thank you very much!!) Every time I tell myself that I feel that way because I don't have enough skills or knowledge to use it properly - regardless, I have just about given up on LINQ to SQL. |
|
|
|
X002548
Not Just a Number
15586 Posts |
|
|
nathans
Aged Yak Warrior
938 Posts |
Posted - 2012-03-24 : 13:51:30
|
| I've also fallen for the L2S myth several times and it always starts with "its like magic!" and ends with impossible to tune performance problems.Has anyone entered the world of micro ORMs? I have had a lot of success with Dapper. It doesnt attempt to automagically construct your tsql queries but still provides great dynamic mapping in the DAL. And in fully supports stored procs :) It might be a middle ground between you and whomever is proposing the L2S.[url]http://code.google.com/p/dapper-dot-net/[/url] |
|
|
|
afrika
Master Smack Fu Yak Hacker
2706 Posts |
Posted - 2012-05-09 : 17:09:36
|
quote:
Originally posted by sunitabeck
LINQ to Object, LINQ to XML, LINQ to DataSet are all nice - I love the syntax and the compact and intuitive nature of it (lambda expressions etc.). But, LINQ To SQL? Ugh!! I feel like I have very little control over the query it generates, and very little control over how it gets executed (lazy loading? no, thank you very much!!) Every time I tell myself that I feel that way because I don't have enough skills or knowledge to use it properly - regardless, I have just about given up on LINQ to SQL.
Although this is a bit old, I think LINQ although is not my cup of tea, it can be useful to applications that could be ported to multiple different databases, and could be useful in rapid application developments and also other uses as stated aboveI have also worked with Microsoft's new ORM entity framework and entity sql, and EF with SP and I love it, makes life as a programmer much better.Ehi |
|
|
|
Transact Charlie
Master Smack Fu Yak Hacker
3451 Posts |
Posted - 2012-05-10 : 05:32:39
|
| I think the topic title is a little misnamed.LINQ as a concept inside .net development is amazing. If you are dealing with collections then link provides a much more declarative way of performing many, many operations. linq is one of the tings I like *the most* about the .net framework.However, linq to sql? I think it can be OK... ish as long as you don't let it do anything complicated. Calling stored proc's with linq is (pretty / really) nice. Just don't try to do anything else with it.Charlie===============================================================Msg 3903, Level 16, State 1, Line 1736The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION |
|
|
|
Sachin.Nand
2937 Posts |
|
|
afrika
Master Smack Fu Yak Hacker
2706 Posts |
Posted - 2012-05-11 : 02:41:18
|
quote:
Originally posted by Sachin.Nand
I think everybody jumping on the bandwagon of praising EF ...
I dont see anyone praising it on this thread ???More like a general discussion |
|
|
|
Sachin.Nand
2937 Posts |
Posted - 2012-05-11 : 12:46:58
|
Then not sure then what is all this...If it is not praising..quote:
Originally posted by afrika....I have also worked with Microsoft's new ORM entity framework and entity sql, and EF with SP and I love it, makes life as a programmer much better.Ehi
quote:
Originally posted by sunitabeck
LINQ to Object, LINQ to XML, LINQ to DataSet are all nice - I love the syntax and the compact and intuitive nature of it (lambda expressions etc.)....
LINQ to SQL or EF or whatever you call it..is good for academic or small to very medium level applications...It is not meant for Enterprise level stuff...It sucks BIG TIME...Good old Visual foxpro retrieves data much faster this EF.Not sure why the heck do application developers want to bring OOPS concept in everything they want to work with..After Monday and Tuesday even the calendar says W T F .... |
|
|
|
|
LINQ