There are caveats, but yes it's nice and KISS. It's superior in many ways to Hibernate since the providers are working with expression trees rather than static queries and thus only fetches the data you need, when you need it. Note though that Microsoft is now officially pushing LINQ-to-Entities rather than LINQ-to-SQL, though that matters little to Mono/DbLinq users.
/Casper On Jul 14, 11:16 am, Moandji Ezana <[email protected]> wrote: > The thing I find most useful about Hibernate is that when you have a lot of > tables of inter-related data, it really alleviates the pain of having to > think about what data you need to load for each possible workflow. > > Has anyone used LINQ? Does that make working with SQL nice enough to do away > with an ORM? > > Moandji -- 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.
