Thanks, Fabio. I am working on a new caching scheme, so I am exploring how to improve query cache coherence. Outside of the standardquerycache.
On Fri, Dec 17, 2010 at 12:04 PM, Fabio Maulo <[email protected]> wrote: > The querycache is invalidated by NH if you are using the default > (standardquerycache) > > On Fri, Dec 17, 2010 at 1:53 PM, Fabio Maulo <[email protected]> wrote: >> >> No. >> >> On Fri, Dec 17, 2010 at 1:43 PM, Aaron Boxer <[email protected]> wrote: >>> >>> I see that the query cache uses a NonstrictReadWrite concurrency >>> strategy. >>> So, queries can get stale. Is it possible to use a stricter strategy? And >>> does >>> it make sense to have some sort of version on the query, some sort of >>> aggregate >>> version from all of the returned entities, so that newer queries don't >>> get clobbered >>> by older queries? >>> >>> Thanks, >>> Aaron >>> >>> -- >>> 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. >>> >> >> >> >> -- >> Fabio Maulo >> > > > > -- > 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. > -- 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.
