Hi Roy, > I would like to override the default cache behavior, so that I can > explicitly invalidate the cache, rather than have it be cleared on > each transaction commit. My use case is that I have a largely > read-only database, and don't want to pay the penalty for a query each > time. Has anyone worked on this problem? Is this a reasonable thing to > do?
This should be easy to handle by simply not committing/rolling back the store. Just allow it to stay within the same transaction for the period you don't care about flushing the cache, and I believe it should all work well. Does that work for you? -- Gustavo Niemeyer http://niemeyer.net http://niemeyer.net/blog http://niemeyer.net/twitter -- storm mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/storm
