i'm not convinced that full time developers for nhibernate would be such a good thing. Right now, none of us work on NHibernate full time, and of course we could always use more help. But the fact that we're all doing _real_ projects is something that i believe is of tremendous value to NHibernate. We run into real issues, just like other NHibernate users do. We run into real usage scenarios, just like other NHibernate users do.
When you work on a specific infrastructure piece of technology full time, it's not always easy to keep an open-minded, or even realistic view with regards to real situations and use cases which occur in real projects. Entity Framework may have some fancy designers, and their documentation will be better, but when will it have all of the core features that NHibernate has? As long as the development team sticks to their vision on data access, that time may never come. Again, while we could always use more help and more contributions, i _personally_ (i'm not speaking for the other developers btw) am very happy with the way NHibernate development happens. On Sat, Jan 31, 2009 at 6:52 PM, MAMMON <[email protected]> wrote: > > Quoting Fabio Maulo (from this post I started in Oct 2007, > > http://groups.google.com/group/nhusers/browse_thread/thread/a50d2076d6bb7caf/c71334053a9a815e?hl=en > ) > > ------------------ > > "Please don't compare NH with EF. > You can't compare 4 crazy dogs with a monster as Microsoft. > Give us the same funds, or a part of it, and then we can make some > comparison. > > BTW EF is the future because Microsoft (the word Microsoft don't need > any > other explication), and NH is the present. " > > ------------------ > > The thing is, comparisons between NH and other products that seek to > solve the same problem HAVE to be made. No one is going to select NH > over EF or Linq2Sql or LLBLGEN because purely by virtue of NH being > the open source underdog. In the case of EF, open source and > licensing probably aren't considerations, because the company is > already using Visual Studio and .NET on Windows platforms. The > comparisons will be made when business are making technology > decisions. > > I don't want EF to be the future, because I think NH is a better > product. But EF has dozens of full time developers, and will > eventually be what people want it to be. NH has the potential to be > better, but needs paid full-time developers to get there. > > Sorry, I know this was off topic.... > > > On Jan 31, 10:44 am, MAMMON <[email protected]> wrote: > > Honestly, I would actually give it a shot, but I am not familiar with > > the NHibernate code base, and I wouldn't know where to start. It > > would take a considerable time investment to become a useful > > contributor to this project. I would be willing to do it, but I work > > full time, do a little bit of part time IT work for family, and have 2 > > music classes at a community college right now. > > > > Also, if I became a contributor to the NH project, I would be brushing > > up on business skills, and writing letters to businesses, seeking > > corporate sponsorship, so that the core NH developers could quit their > > other jobs (if willing), and develop NH full time. > > > > On Jan 30, 5:36 pm, Ayende Rahien <[email protected]> wrote: > > > > > Mammon,You are correct, I forgot about that issue. > > > You are welcome to fix the problem :-) > > > > > On Fri, Jan 30, 2009 at 12:23 PM, MAMMON <[email protected]> wrote: > > > > > > I know. That's what I said in the first place, linking back to the > > > > original thread in this group that illustrated the problem. In this > > > > current thread, Ayende made this suggestion: > > > > > > CreateMutliQuery(). > > > > .AddSqlQuery("") > > > > .AddSqlQuery("exec ReturnsTwoResultSet") > > > > > > And I was questioning if it would work, since it has been previously > > > > pointed out that the IMultiCriteria and IMultiQuery implementations > > > > currently only support HQL. > > > > > > On Jan 30, 10:17 am, Fabio Maulo <[email protected]> wrote: > > > > > 2009/1/30 MAMMON <[email protected]> > > > > > > > > Right, but if you have named queries that are EXECing stored > > > > > > procedures, and you create a MutliQuery, and add multiple named > > > > > > queries that are using stored procedures, it won't work. > > > > > > > As I said MultiQuery is only for HQL. SPs are not HQL. > > > > > -- > > > > > Fabio Maulo > > > -- Davy Brion http://davybrion.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
