On 15.05.11 14:13, Graham Leggett wrote: > I am aware that torque supports caching, but I don't like caching as a > solution, as I want the status object created within the same > transaction as the original query.
For status entries like these, caching is always my recommended solution. We have hit rates of over 99% with the Torque built-in cache. The solution you suggest is more or less the same thing that the cache does. If you need help with the implementation, I'm happy to share my experiences. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
