Hi Rick, I have never used rhino-security, so I can't be 100% sure about the rammification. But as far as I can see the only place where data access code lives is in that repository.
There are two options: - evict the whole query cache after each change (this has some performance implications when you're doing a lot of updates/reads at the same time, because after each update the whole query cache is evicted) - split the queries in different cache regions (using SetCacheRegion) and evict that regions query cache whenever an update occurs which should invalidate that region. If you can write the failing tests, I can implement selective query eviction like I did for the first test you wrote. (https://github.com/remcoros/rhino-security) Also maybe Nathan can have a look at this? Remco -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en.
