On Sat, 2 Feb 2008, Christopher Arndt wrote:
> Richard Jones schrieb:
> > In short, the scheduled action does fire, but any changes made during
> > its execution - either modifying the change request status or creating
> > the new PCMAccount table row - are not committed to the database.
>
> You probably have to commit your database changes in the "do_activet"
> function manually. In TG 1 every controller method is wrapped in an
> implicit transaction, which do the commit for you. But since the
> scheduler is not run by the TurboGeras controller methods, you have to
> handle transactions manually.
Sorry, I should have mentioned that I tried wrapping the function in
hub.begin() and hub.end() but that didn't help.
Hmm, I just re-read the docs, and though it's not explicitly shown I guess
there's a hub.commit() I should have been calling...
I'll give that a try when I'm sitting at the code again.
Thanks,
Richard
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
