Adavantager of LINQ ?
-
hi Can any one let me know about the adavantages of LINQ for end user who is using our application, thanks in advance.
For the end user the advantages are not obvious, since most of the benefits go to the developer. 1) faster development time - quicker results, lower cost of development 2) more stable - compile time checking and type-safe code means no more embedded SQL strings means fewer runtime errors
'Howard
-
For the end user the advantages are not obvious, since most of the benefits go to the developer. 1) faster development time - quicker results, lower cost of development 2) more stable - compile time checking and type-safe code means no more embedded SQL strings means fewer runtime errors
'Howard
Howard Richards wrote:
no more embedded SQL strings means fewer runtime errors
Let's not forget the benefit of protecting against SQL Injections due to hardcoded SQL statements.
Deja View - the feeling that you've seen this post before.
-
Howard Richards wrote:
no more embedded SQL strings means fewer runtime errors
Let's not forget the benefit of protecting against SQL Injections due to hardcoded SQL statements.
Deja View - the feeling that you've seen this post before.
Excellent point, Pete.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
-
For the end user the advantages are not obvious, since most of the benefits go to the developer. 1) faster development time - quicker results, lower cost of development 2) more stable - compile time checking and type-safe code means no more embedded SQL strings means fewer runtime errors
'Howard
I am also just getting my feet wet in LINQ, and I see the advantages you list. However, I'm still stuck with the "it's better because it is easier for the developer", which doesn't quite seal the deal for me. In terms of real world applications, how does LINQ fare performance-wise and memory-wise? Specific example, I have an application which performs calculations based on a user-provided data file which could be on the order of 20Gb to 30Gb in size. The application also uses a couple of data files we provide that are needed for the calculation, and the results are retained in an encrypted file. Various steps in the process scan through the input files to pull out data needed to aggregate the results as the calculation progresses. (...this is a very poor and rudimentary description, however it's best I can do due to the nature of the project...) In any case, originally I would read into DataSets and use them for the filtering and querying I needed for the calculation. I found these to be way too memory expensive. I've switched to SortedLists, which work great and provide a much leaner memory and performance profile. So, can LINQ help me here? Would it be better, or just different? Better for the application, or just better for me the developer? Cheers, Carl
-
I am also just getting my feet wet in LINQ, and I see the advantages you list. However, I'm still stuck with the "it's better because it is easier for the developer", which doesn't quite seal the deal for me. In terms of real world applications, how does LINQ fare performance-wise and memory-wise? Specific example, I have an application which performs calculations based on a user-provided data file which could be on the order of 20Gb to 30Gb in size. The application also uses a couple of data files we provide that are needed for the calculation, and the results are retained in an encrypted file. Various steps in the process scan through the input files to pull out data needed to aggregate the results as the calculation progresses. (...this is a very poor and rudimentary description, however it's best I can do due to the nature of the project...) In any case, originally I would read into DataSets and use them for the filtering and querying I needed for the calculation. I found these to be way too memory expensive. I've switched to SortedLists, which work great and provide a much leaner memory and performance profile. So, can LINQ help me here? Would it be better, or just different? Better for the application, or just better for me the developer? Cheers, Carl
Any toolkit that makes it easier for the developer is going to benefit the client. The other option is developing equivalent functionality in house, and I am yet to see an in-house data layer that didnt make me cringe in disgust. Wouldn't you expect your mechanic to use the best tool for the job so they can get the job done quicker without resorting to dodgy hacks with a monkey-wrench and fencing wire? ;) Your specific scenario suggests that fast database lookups are in order. BerkelyDB is very expensive (for non-GPL use), but also very fast. I doubt the flexibility that LINQ offers is going to help you a great deal, especially if your processing code is already implemented.
Mark Churchill Director, Dunn & Churchill Pty Ltd Free Download: Diamond Binding: The simple, powerful, reliable, and effective data layer toolkit for Visual Studio.
Alpha release: Entanglar: Transparant multiplayer framework for .Net games.