Jared Kuolt <[EMAIL PROTECTED]> writes: > I just have to wrap it with hub.being() and hub.commit() and it works > but I got really frustrated trying to figure that out. > > Thoughts?
I think this change is surprising everyone and making some parts of TG unusable without resorting to other tools (such as creating users to use with the identity framework). I prefer changing this implicit transaction behaviour to some sort of decorator or filter that can be enabled and disabled at the configuration file... Reversing it should also be OK (at least I still have my own hub.begin() & co. where it is needed; all of my critical tables have cache disabled so that I don't suffer the cache problem (besides wrapping then with transactions, but I dunno if this is necessary after disabling cache)). I don't have any solution to the problem, but is it really worth it? Having implicit transactions and having to commit them *outside* of any method is really weird... -- Jorge Godoy <[EMAIL PROTECTED]>
