My advise: 1) IRepository (*no queriable*) 2) concrete Repository implementation queriable (implements IQueriable) 3) inside the Repository impl. you are in the "safe area" (the other part of the app. does not know NH) 4) depending on the query you can use: LINQ (new in NH3), HQL, QueryOver, SQL
Do you remember that old times when people said "to write SQL incrustated in the code, everywhere, is a really bad practices" ? well... which is the difference with a LINQ sentence to go to persistence ? The Repository/DAO is the responsible of DataAccess and one of its most important responsibility is the construction of the query. If you move this responsibility out side the Repository/DAO impl you will have the same identical issue than write SQL everywhere. On Fri, Jun 18, 2010 at 2:53 AM, Tomasz Modelski (IDev) < [email protected]> wrote: > I'm using NH trunk version, rev. 4790 from 12.04.2010 on my production > application, application is still under heavy development and > deployment (we are working something like agile iterations). > We are forced to use all NH query providers :-). > > There are some situations where old LinqToNH works better then new > one :-) > there are some situations where new LingToNh works better then old > one :-). > 'Hidden powers' are in new QueryOver api. It's criteria api in Linq/ > labda style. It works very good, almost error free, but still have > limitations. > And hql is the last ultimate solution for all weird raporting queries > with grouping, HAVING, IN / NOT IN etc. > > It would be nice to hear some status report from NH team, maybe some > blog entry. > > Maybe someone from LinqToNH team could make some page / blog entry > with examples of working & not working queries using new LinqToNH and > QueryOver. > It would be very helpfull. > > regards, Tomasz Modelski. > > ps. lately, I steadily check the > http://sourceforge.net/projects/nhibernate/develop > page to see if there are some major Linq improvements and when it's > worth to get & compile latest trunk. > > On 18 Cze, 01:09, Jeffry Morris <[email protected]> wrote: > > Yes, by my usage scenarios have been very simple to date. Simple joins > and > > projections. I can say that I already surpassed some of the limitations > in > > the older provider, which couldn't even do a join. > > > > By this time next month, I'll know more... > > > > On Thu, Jun 17, 2010 at 3:49 PM, Craig van Nieuwkerk <[email protected] > >wrote: > > > > > > > > > Have you been able to use Linq almost exclusively for writing queries > > > now, or do you still go back to ICriteria and HQL occasionally? > > > > > On Fri, Jun 18, 2010 at 7:00 AM, Jeffry Morris <[email protected] > > > > > wrote: > > > > It's merged with the trunk for NHibernate 3...I have been using it > for a > > > few > > > > weeks and I am very happy :) > > > > > -- > > > 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]<nhusers%[email protected]> > <nhusers%[email protected]<nhusers%[email protected]> > > > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/nhusers?hl=en.- Ukryj cytowany tekst - > > > > - Pokaż cytowany tekst - > > -- > 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]<nhusers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > > -- Fabio Maulo -- 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.
