On 3/27/06, Jorge Godoy <[EMAIL PROTECTED]> wrote: > There's also an issue with threading and cache. I don't know the status of > this implementation for TurboGears, but I believe you have to disable caching > by hand:
This should not really be an issue any more. TurboGears 0.9 uses implicit transactions... each request gets into a transaction that either commits or rolls back at the end of the request. The way this works within SQLObject turns out to be somewhat "unit of work" style, and you effectively have a cache that exists *just for a single request*. Kevin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
