Hi Rick, I don't use Rhino Security, but I have come accros the same issue when using NHibernate.
As stated in this thread: http://groups.google.com/group/rhino-tools-dev/browse_thread/thread/c7c8e448c82539a1/f80ee6cebe65e1a9?lnk=gst&q=second+cache#f80ee6cebe65e1a9 it has something to do with the entity not owning the collection, so the query cache doesn't get signaled of the changes to the collection. I have fixed this issue before by making use of different cache regions and evicting all queries of this cache region. It isn't a very elegant solution. But if you can keep track of where and when a cache region is used and when you need to clear it (ie. everything in 1 repository) it works. Have a look at my last commit: https://github.com/remcoros/rhino-security/commits/master Also note that I have added equality overrides to the User class in the test project. THIS IS REALLY IMPORTANT. else the Users.Remove() call won't find the correct instance (altough they have the same Id, they are different references!). Take my commit as an example for applying this to the other methods/entities too. Hope this helps. btw, I won't charge you, lol :). Instead make a donation to a local charity organization in your neigbourhood. Remco Ros -- 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.
