Re: Why use ActiveRecord For LINQ??
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 release to fool more prospective users. And of course we will also delete the all sources then, so that no one can update the products themselves - after all that's the nature of every open source project. Truth, James Biased, Markus --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Castle Project Users group. To post to this group, send email to castle-project-users@googlegroups.com To unsubscribe from this group, send email to castle-project-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~--~~~~--~~--~--~---
Re: Why use ActiveRecord For LINQ??
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 expressions (from ... where ... select...). Everything underneath (AR/NH/RDBMS) stays the same. -Markus --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Castle Project Users group. To post to this group, send email to castle-project-users@googlegroups.com To unsubscribe from this group, send email to castle-project-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~--~~~~--~~--~--~---
Re: Why use ActiveRecord For LINQ??
Only Linq to Sql is dead, Microsoft killed it to make room for the Entity Framework that in turn is also a Linq provider. So you could argue (although I think the entity framework is far from a usable state) that you could also use Entity Framework for your MS Stack Linq needs. greetings Daniel On Thu, May 28, 2009 at 6:51 AM, John Simons johnsimons...@yahoo.com.auwrote: Another con of (3) is LinqToSql is dead ( http://ayende.com/Blog/archive/2008/10/31/microsoft-kills-linq-to-sql.aspx ) -- *From:* James Curran james.cur...@gmail.com *To:* castle-project-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 - NH - MSSQL, et al. 3) LINQ - MSSQL What are the pro cons of each option. One con of (3) is that it's primarily limited to MSSQL (although providers for other DBs are available at varying stability), but that's essentially a binary option: It's either irrelevant (if you are using MSSQL) or immediately disqualifying (if you use some other DB) -- Truth, James On Thu, May 28, 2009 at 12:10 AM, Markus Zywitza markus.zywi...@gmail.com wrote: 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 powers of NHibernate and the IntelliSense of a LINQ-Provider. -- Need a Holiday? Win a $10,000 Holiday of your choice. Enter now.http://us.lrd.yahoo.com/_ylc=X3oDMTJxN2x2ZmNpBF9zAzIwMjM2MTY2MTMEdG1fZG1lY2gDVGV4dCBMaW5rBHRtX2xuawNVMTEwMzk3NwR0bV9uZXQDWWFob28hBHRtX3BvcwN0YWdsaW5lBHRtX3BwdHkDYXVueg--/SIG=14600t3ni/**http%3A//au.rd.yahoo.com/mail/tagline/creativeholidays/*http%3A//au.docs.yahoo.com/homepageset/%3Fp1=other%26p2=au%26p3=mailtagline . --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Castle Project Users group. To post to this group, send email to castle-project-users@googlegroups.com To unsubscribe from this group, send email to castle-project-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~--~~~~--~~--~--~---
Why use ActiveRecord For 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 What does AR offer that LINQ does not? The answer to that might be contained in the next: If I'm using AR, why use AR4LINQ rather than just use AR directly to the database? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Castle Project Users group. To post to this group, send email to castle-project-users@googlegroups.com To unsubscribe from this group, send email to castle-project-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~--~~~~--~~--~--~---
Re: Why use ActiveRecord For LINQ??
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 powers of NHibernate and the IntelliSense of a LINQ-Provider. -Markus 2009/5/28 James Curran james.cur...@gmail.com: On Wed, May 27, 2009 at 10:13 PM, Alex Henderson bitterco...@gmail.com wrote: When you say Linq, are you referring to Linq2Sql or Linq2objects? Linq2Sql (I'm using Linq2Objects also, but I figured that's irrelevant to the topic) -- Truth, James --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Castle Project Users group. To post to this group, send email to castle-project-users@googlegroups.com To unsubscribe from this group, send email to castle-project-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~--~~~~--~~--~--~---
Re: Why use ActiveRecord For LINQ??
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 blindly on results coming from some a legacy DAO they've written *shudder* where to their mind they are doing Linq, but only by name rather then in spirit. On Thu, May 28, 2009 at 4:10 PM, Markus Zywitza markus.zywi...@gmail.comwrote: 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 powers of NHibernate and the IntelliSense of a LINQ-Provider. -Markus 2009/5/28 James Curran james.cur...@gmail.com: On Wed, May 27, 2009 at 10:13 PM, Alex Henderson bitterco...@gmail.com wrote: When you say Linq, are you referring to Linq2Sql or Linq2objects? Linq2Sql (I'm using Linq2Objects also, but I figured that's irrelevant to the topic) -- Truth, James --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Castle Project Users group. To post to this group, send email to castle-project-users@googlegroups.com To unsubscribe from this group, send email to castle-project-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~--~~~~--~~--~--~---
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 - NH - MSSQL, et al. 3) LINQ - MSSQL What are the pro cons of each option. One con of (3) is that it's primarily limited to MSSQL (although providers for other DBs are available at varying stability), but that's essentially a binary option: It's either irrelevant (if you are using MSSQL) or immediately disqualifying (if you use some other DB) -- Truth, James On Thu, May 28, 2009 at 12:10 AM, Markus Zywitza markus.zywi...@gmail.com wrote: 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 powers of NHibernate and the IntelliSense of a LINQ-Provider. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Castle Project Users group. To post to this group, send email to castle-project-users@googlegroups.com To unsubscribe from this group, send email to castle-project-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~--~~~~--~~--~--~---
Re: Why use ActiveRecord For LINQ??
Another con of (3) is LinqToSql is dead (http://ayende.com/Blog/archive/2008/10/31/microsoft-kills-linq-to-sql.aspx) From: James Curran james.cur...@gmail.com To: castle-project-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 - NH - MSSQL, et al. 3) LINQ - MSSQL What are the pro cons of each option. One con of (3) is that it's primarily limited to MSSQL (although providers for other DBs are available at varying stability), but that's essentially a binary option: It's either irrelevant (if you are using MSSQL) or immediately disqualifying (if you use some other DB) -- Truth, James On Thu, May 28, 2009 at 12:10 AM, Markus Zywitza markus.zywi...@gmail.com wrote: 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 powers of NHibernate and the IntelliSense of a LINQ-Provider. Need a Holiday? Win a $10,000 Holiday of your choice. Enter now.http://us.lrd.yahoo.com/_ylc=X3oDMTJxN2x2ZmNpBF9zAzIwMjM2MTY2MTMEdG1fZG1lY2gDVGV4dCBMaW5rBHRtX2xuawNVMTEwMzk3NwR0bV9uZXQDWWFob28hBHRtX3BvcwN0YWdsaW5lBHRtX3BwdHkDYXVueg--/SIG=14600t3ni/**http%3A//au.rd.yahoo.com/mail/tagline/creativeholidays/*http%3A//au.docs.yahoo.com/homepageset/%3Fp1=other%26p2=au%26p3=mailtagline --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Castle Project Users group. To post to this group, send email to castle-project-users@googlegroups.com To unsubscribe from this group, send email to castle-project-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~--~~~~--~~--~--~---
