Sorry... there is a prerequisite...The work must be followed by, at least, a NH team committers. We must check quality and that the project are following the target of LINQ2NH of the trunk. To be clear... To work with LINQ, or have a similar and very closer result, so far we have 2 existing project: - NHibernate.LINQ on Contrib - NH-lamda-criteria in google code
I would like to be sure that the new project can be added to the trunk; perhaps Chad or Oren can follow the development of the new project. To you the final decision. 2009/1/9 Fabio Maulo <[email protected]> > 2009/1/9 Chad Lee <[email protected]> > >> Sounds good to me. How would this fit in with Fabio's Artorius? Isn't >> that a prerequisite to getting Linq to NH working in the trunk? > > > There is not a prerequisite. > Sure, when Artorius have its QueryTranslator working the work of a possible > LINQ2NH would be only a ExpressionTree converter and believe me that is more > easy than translate the ExpressionTree to SQL. > More than that LINQ2NH need "some" extensions to support al HQL feature as, > for example, "join fetch", "with" clause, "elements", "embedded properties" > as "count", "id".... without talk about "registrable" HQL function for each > dialiact. > > Who want can start, or better "re-start", the work on LINQ2NH and we will > happy with the result. > > When Artorius is ready to be "injected" in the trunk we can think about > what we want/must do. > > -- > Fabio Maulo > > P.S. even if I'm working it I'm not considerer Artorius as MY product; it > is a NH team product. > -- Fabio Maulo
