On Friday, February 5, 2016 at 3:38:17 PM UTC-8, Dave S wrote: > > On Friday, February 5, 2016 at 1:23:32 AM UTC-8, Niphlod wrote: >> >> you're translating my "like" as in "exactly". and making assumptions, >> wrong ones. >> > > I'm not sure I'm straying that far. Your further explanation, below, I > think describes my current understanding. > > What I was missing in my comments about queuing from a shell is needing to > do db.commit(). I finally tried that, and the task ran. The reason I was > interested in that was to test fire the task. The conditional queuing is > something that I had already gone ahead with, putting it in the model > (outside the task function, so at the "top" level), and that seems to be > working, too. > > > >> I just said that the environment in which the scheduler executes your >> task is LIKE a shell one, where you launch the FUNCTION you queued, and >> then exit the shell. >> >> At the very "raw" structure of the scheduler, it just see if there are >> tasks ready to be processed, opens a shell env, executes the function, >> records the output, closes the shell. for every task. >> > > Despite the stumbles I've made, I think I've gotten there. > > And I appreciate your help inf finding the correct path.
/dps -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
