And in NHibernate Land
This is just an update. Fabio has been porting large swathes of Hibernate 3.2, Paul is dealing with the continued port of Hibernate Search while Dario has focused on porting Hibernate Validator. He has also just started to port Hibernate Shards, which is going to make things very interesting indeed.
Me? I am sitting in the corner, admiring the work and occasionally shouting hurray!
Comments
Ayende,
Are there any official plans for NHibernate.Linq? I tried it out and it seemed to be working pretty well :)
Cheers,
Nicko
Alive an well, we want to merge it into the build, certainly.
Ayende,
I corresponded with you previously about Linq to Nhibernate, and I'm just now circling back to this topic again, as my project is starting to head in that direction again... I'd like to know, does NHibernate.Linq map to the ICriteria interface, or does it use SQL/HQL?
Also, does its use require the consuming code to have a reference to NHibernate? My primary reason for wanting NHibernate.Linq so badly is that one of our design goals for the project I'm on is to use NHibernate, but in such a way that none of our consuming code has to know it's using NHibernate (we've done a bridge pattern with a generic abstract repository to insulate ourselves from NH).
Also, I guess the $64,000 question is, when will NH 2.0 be released?
I'm finally going to start learning this Linq stuff, and I might perhaps be able to help with NHibernate.Linq soon, but I have to be able to justify it with my team (ie, making sure its objectives are consistent/complementary with ours).
Thanks, and keep up the great work,
James
Linq to NH uses the criteria API.
It doesn't require a reference to NH.dll, but it will require a reference to NH.Linq.dll
I don't want to give dates for NH 2.0
Comment preview