http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Yeah,Thanks,My from China. http://ayende.com/4083/nhibernate-linq-1-0-released#comment49http://ayende.com/4083/nhibernate-linq-1-0-released#comment49Tue, 08 Sep 2009 09:30:03 GMTGreat work ... thanks guys.. I have came across this atricle [chadly.net/.../...-Pitfalls-of-NHibernateLinq.aspx](http://chadly.net/post/2009/08/26/The-Many-Pitfalls-of-NHibernateLinq.aspx) ... can you please confirm those pitfalls ? http://ayende.com/4083/nhibernate-linq-1-0-released#comment48http://ayende.com/4083/nhibernate-linq-1-0-released#comment48Sun, 06 Sep 2009 11:14:05 GMTGreat, I will definitely use it too! http://ayende.com/4083/nhibernate-linq-1-0-released#comment47http://ayende.com/4083/nhibernate-linq-1-0-released#comment47Tue, 25 Aug 2009 06:08:55 GMTGreat, gotta try this! http://ayende.com/4083/nhibernate-linq-1-0-released#comment46http://ayende.com/4083/nhibernate-linq-1-0-released#comment46Mon, 17 Aug 2009 14:23:33 GMT@Laurens: Did you try myString.Contains("blabla")? This should work without problems. http://ayende.com/4083/nhibernate-linq-1-0-released#comment45http://ayende.com/4083/nhibernate-linq-1-0-released#comment45Thu, 13 Aug 2009 15:02:00 GMTLinq requires .Net 3.5 http://ayende.com/4083/nhibernate-linq-1-0-released#comment44http://ayende.com/4083/nhibernate-linq-1-0-released#comment44Sun, 09 Aug 2009 19:34:45 GMTcan i use with .net 2.0 ? or have to install .net 3.5 http://ayende.com/4083/nhibernate-linq-1-0-released#comment43http://ayende.com/4083/nhibernate-linq-1-0-released#comment43Sun, 09 Aug 2009 16:57:46 GMTI am using Active record which implements linq to nhibernate. It is working perfectly. The only thing is I can't find an 'Like' operator. Can you tell me how to perform a 'like' clause. http://ayende.com/4083/nhibernate-linq-1-0-released#comment42http://ayende.com/4083/nhibernate-linq-1-0-released#comment42Wed, 05 Aug 2009 12:12:39 GMTJohn, I have no idea, but it should http://ayende.com/4083/nhibernate-linq-1-0-released#comment41http://ayende.com/4083/nhibernate-linq-1-0-released#comment41Sun, 02 Aug 2009 19:20:05 GMTIs there going to be a mono version? http://ayende.com/4083/nhibernate-linq-1-0-released#comment40http://ayende.com/4083/nhibernate-linq-1-0-released#comment40Sun, 02 Aug 2009 01:38:43 GMTIt could, but that is not exposed currently http://ayende.com/4083/nhibernate-linq-1-0-released#comment39http://ayende.com/4083/nhibernate-linq-1-0-released#comment39Sat, 01 Aug 2009 06:34:02 GMTCan the Linq provider be used with Second Level Cache? Roberto.- http://ayende.com/4083/nhibernate-linq-1-0-released#comment38http://ayende.com/4083/nhibernate-linq-1-0-released#comment38Sat, 01 Aug 2009 02:16:24 GMTThanks - we'll do this. Concerning hidden assumptions: - Tests must run in identical conditions. If this is not possible, all the differences must be described explicitly (that's why I need your help). - The measured cases must expose some real-life scenarios. E.g. above test with proxies is obviously non-realistic. I can't imagine application constantly generating proxies without re-using them - it's really the way to get OutOfMemoryException. - In general, I dislike overall or weighted scores for test sequences. A lot depends on which features are chosen to be scored and their scale numbers here, so it's better to simply show all the particular results and allow users to choose what's more important for them by their own way. If these conditions are satisfied, I believe in tests ;) Obviously, real-life application results can differ, but complete contrast to tests is rare. So at least, tests show you what you might expect / what must be tuned up. http://ayende.com/4083/nhibernate-linq-1-0-released#comment37http://ayende.com/4083/nhibernate-linq-1-0-released#comment37Wed, 29 Jul 2009 16:22:32 GMTHi, In general, I don't like benchmarks: [ayende.com/.../Trusting-the-benchmark.aspx](http://ayende.com/Blog/archive/2007/10/16/Trusting-the-benchmark.aspx) Mostly because there are a lot of hidden assumptions that are going to bite you when you do things with them. You can send me the code and I'll review it, yes. About Linq. It is RTM because we have seen people use it in production for years. I am not surprised that a lot of the tests fail, tests tend to try to find the edge cases. This is not what this release it about. It is about providing a linq provider that can solve a large amount of the day to day stuff that people are using. We are planning of writing a full featured linq provider, but that would be for the next version, and use a different approach. http://ayende.com/4083/nhibernate-linq-1-0-released#comment36http://ayende.com/4083/nhibernate-linq-1-0-released#comment36Wed, 29 Jul 2009 15:12:55 GMTHello Ayende, We've made some preliminary comparisons related to LINQ and NHibernate performance. For now we're comparing it just with DO4, but later more comprehensive results will appear. Anyway, current results aren't very optimistic: [blog.dataobjects.net/.../...rmance-comparison.html](http://blog.dataobjects.net/2009/07/preliminary-orm-performance-comparison.html) The question is: can we contact you to help us with making our NHibernate-related tests fully honest? I mean probably we missed some option we must turn on or off, etc.? We expect we'll be able to share the results (source code, etc.) by the end of the next week. Concerning LINQ: well, it's released, but I think it would be more honestly to call this as CTP or something like this. ~ 75% of our tests fail for LINQ features fail on NH. My impression is that only very basic stuff like Where works. What about Join, GroupJoin, SelectMany, First/Single in subqueries, etc.? http://ayende.com/4083/nhibernate-linq-1-0-released#comment35http://ayende.com/4083/nhibernate-linq-1-0-released#comment35Wed, 29 Jul 2009 15:04:52 GMTGreat! Great! http://ayende.com/4083/nhibernate-linq-1-0-released#comment34http://ayende.com/4083/nhibernate-linq-1-0-released#comment34Wed, 29 Jul 2009 07:05:07 GMTThanks Ayende Rhien! NHibernate.LinQ make NHibernate tronger than ever. http://ayende.com/4083/nhibernate-linq-1-0-released#comment33http://ayende.com/4083/nhibernate-linq-1-0-released#comment33Tue, 28 Jul 2009 08:37:31 GMTThis is epic - congrats everyone on a job well done. http://ayende.com/4083/nhibernate-linq-1-0-released#comment32http://ayende.com/4083/nhibernate-linq-1-0-released#comment32Tue, 28 Jul 2009 04:41:27 GMTGraham, It doesn't work. I just tried is on a very small app (NerdDinner), and it doesn't work even there. OR/M are not interchangable. http://ayende.com/4083/nhibernate-linq-1-0-released#comment31http://ayende.com/4083/nhibernate-linq-1-0-released#comment31Mon, 27 Jul 2009 21:28:24 GMTMatt, Ask your software architect why he didn't design a swappable repository layer so it doesn't matter if you use EF or NH... not hard to do, just takes a lot of discipline... See what he says :) (or duck quickly !) http://ayende.com/4083/nhibernate-linq-1-0-released#comment30http://ayende.com/4083/nhibernate-linq-1-0-released#comment30Mon, 27 Jul 2009 20:17:38 GMTNice, will have to give this a try http://ayende.com/4083/nhibernate-linq-1-0-released#comment29http://ayende.com/4083/nhibernate-linq-1-0-released#comment29Mon, 27 Jul 2009 19:14:39 GMTVery cool! I will definitely use this. http://ayende.com/4083/nhibernate-linq-1-0-released#comment28http://ayende.com/4083/nhibernate-linq-1-0-released#comment28Mon, 27 Jul 2009 19:00:27 GMTThis is fantastic news, maybe I can finally convince my software architect's to ditch EF and move to nHibernate!! http://ayende.com/4083/nhibernate-linq-1-0-released#comment27http://ayende.com/4083/nhibernate-linq-1-0-released#comment27Mon, 27 Jul 2009 18:33:58 GMTJohn, No, it will not http://ayende.com/4083/nhibernate-linq-1-0-released#comment26http://ayende.com/4083/nhibernate-linq-1-0-released#comment26Mon, 27 Jul 2009 15:26:05 GMTYes, it would http://ayende.com/4083/nhibernate-linq-1-0-released#comment25http://ayende.com/4083/nhibernate-linq-1-0-released#comment25Mon, 27 Jul 2009 15:25:37 GMTIs this just for NH 2.1 or will it work with 2.0, being ICriteria based and all...? http://ayende.com/4083/nhibernate-linq-1-0-released#comment24http://ayende.com/4083/nhibernate-linq-1-0-released#comment24Mon, 27 Jul 2009 14:40:45 GMTSweet! Will this work with Fluent NHibernate out of the box? http://ayende.com/4083/nhibernate-linq-1-0-released#comment23http://ayende.com/4083/nhibernate-linq-1-0-released#comment23Mon, 27 Jul 2009 14:31:08 GMTpb, looks like, can you try in a different browser? http://ayende.com/4083/nhibernate-linq-1-0-released#comment22http://ayende.com/4083/nhibernate-linq-1-0-released#comment22Mon, 27 Jul 2009 13:59:59 GMTSo am I the only one that is getting corrupt zip file messages when trying to download the 2.1.0 NHibernate binary file required to use this LINQ provider? http://ayende.com/4083/nhibernate-linq-1-0-released#comment21http://ayende.com/4083/nhibernate-linq-1-0-released#comment21Mon, 27 Jul 2009 13:57:10 GMTSubqueries in select clauses are supported in NH 2.1 [http://nhjira.koah.net/browse/NH-1359](http://nhjira.koah.net/browse/NH-1359) Are you saying that despite this support, LINQ subqueries still won't work? http://ayende.com/4083/nhibernate-linq-1-0-released#comment20http://ayende.com/4083/nhibernate-linq-1-0-released#comment20Mon, 27 Jul 2009 13:06:42 GMT