I can't see in the example the part of updating the counter. It just takes care that the updates won't result in cache invalidation but the database will still get a hit on each and every counter update, right?
On Jul 28, 4:06 pm, Fabio Maulo <[email protected]> wrote: > This solution was used even to solve the "same" > problem:http://fabiomaulo.blogspot.com/2009/04/tuning-nhibernate-tolerant-que... > > <http://fabiomaulo.blogspot.com/2009/04/tuning-nhibernate-tolerant-que...>The > counter is the counter of visits of a publication. > > 2009/7/28 efic1 <[email protected]> > > > > > > > Hi, > > In my application I have a business entity that needs to include a > > counter of reads and this counter is the only property in the class > > that needs to get updated. > > > I want over the 2nd level cache options and it seems that none of the > > existing solutions supports the ability to separate the database > > update call from the NH commit transaction call. > > > The optimal solution that I'm looking is to have NH update the counter > > in the cache and when the instance get's removed from the cache to > > update the database (increment the counter). > > > Any ideas? > > > Thanks > > -- > 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 -~----------~----~----~----~------~----~------~--~---
