2009/5/31 James Curran james.cur...@gmail.com:
That not particularly relevant. Yes, MS has said that there won't be
anymore updates to Linq2Sql--- However, AR NH are open-source
projects --- Updates to them can stop at any moment without any
notice.Of course -- we are only pretending to
2009/5/28 James Curran james.cur...@gmail.com:
1) AR - NH - MSSQL (plus others, which we'll ignore for now)
2) AR - LINQ - NH - MSSQL, et al.
It's rather:
LINQ - AR - NH - RDBMS
In option 1, you can query the DB with HQL and (Detached)Criteria
queries. In 2, you can also use LINQ query
-users@googlegroups.com
*Sent:* Thursday, 28 May, 2009 2:38:14 PM
*Subject:* Re: Why use ActiveRecord For LINQ??
But I think that changes the terminology more than the underlying question.
We have the options:
1) AR - NH - MSSQL (plus others, which we'll ignore for now)
2) AR - LINQ
I'm using Monorail/Windsor but not ActiveRecord. For my data access,
I'm using LINQ directly. It seemed to me the LINQ and AR do
essentially the same thing.
Lately, I've been hearing a lot about ActiveRecord For LINQ on this
(actually the Devel) mailing list. This raises some questions
Wrong question, wrong answer...
It's neither Linq2SQL nor Linq2objects. L2SQL is not only LINQ but a
LINQ provider on top of MS mapping wizards. LINQ2AR is a wrapper
around LINQ2NH (or NHLinq), which are LINQ providers for NHibernate.
In the end, it means that you can use ActiveRecord with the
Wrong answer, that's a bit harsh :) - I was just trying to clarify what they
were referring to as Linq (because it obviously wasn't the blanket concept
of a language integrated query) - I wasn't attempting to answer the
question... I have actually seen the odd developer using Linq for objects
But I think that changes the terminology more than the underlying question.
We have the options:
1) AR - NH - MSSQL (plus others, which we'll ignore for now)
2) AR - LINQ - NH - MSSQL, et al.
3) LINQ - MSSQL
What are the pro cons of each option.
One con of (3) is that it's primarily
use ActiveRecord For LINQ??
But I think that changes the terminology more than the underlying question.
We have the options:
1) AR - NH - MSSQL (plus others, which we'll ignore for now)
2) AR - LINQ - NH - MSSQL, et al.
3) LINQ - MSSQL
What are the pro cons of each option.
One con of (3
