LINQ is about as closely tied to databases as the concept of null values in Java. Yes, databases use null values, but I don't immediately think "aha, database!" when I see a null used in source code.
Essentially, it's just a convenient tool for building expression trees, encompassing a lot of ideas from declarative programming (which includes FP). The fact that these expressions can be nicely mapped to SQL is almost incidental - it is *so* much more than that! On 15 November 2010 12:21, Casper Bang <[email protected]> wrote: > On Nov 15, 12:06 pm, Ricky Clarkson <[email protected]> wrote: > > Actually, LINQ is just language-integrated queries and has nothing to > > do with databases. I've used it with collections (using System.Linq;) > > resulting in code like: > > Exactly, as I already mentioned - think of it as a build-in JDBC > provider that lets you query anything in one uniform way directly in > the language. Unfortunately a lot of people think of it as an ORM, > missing out on the fact that there's captured intent in an AST > underneath, which can be transformed and evaluated by any available > provider. A genius stroke by monad Meijer for sure. > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<javaposse%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > > -- Kevin Wright mail / gtalk / msn : [email protected] pulse / skype: kev.lee.wright twitter: @thecoda -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
