I really like this idea in concept. My query would literally be just a wrapper at that point, what would be the appropriate place to do this? What would I need to do to the query to make it behave with the cache.
Again thanks for the idea, I think this could be a simple way to use the caches. On Tue, Aug 18, 2015 at 8:31 PM, Yonik Seeley <ysee...@gmail.com> wrote: > On Tue, Aug 18, 2015 at 8:19 PM, Jamie Johnson <jej2...@gmail.com> wrote: > > when you say a security filter, are you asking if I can express my > security > > constraint as a query? If that is the case then the answer is no. At > this > > point I have a requirement to secure Terms (a nightmare I know). > > Heh - ok, I figured as much. > > So... you could also wrap the main query and any filter queries in a > custom security query that would contain the user, and thus still be > able to use filter and query caches unmodified. I know... that's only > a small part of the problem though. > > -Yonik >
