I believe I just stumbled on the same problem last night. I was upgrading an app with an old scheduler (1.99.2) to current (2.4.2). I temporarily solved it by continuing to insert the db record manually, as I needed to finish this quickly and had no time to troubleshoot... I'll be able to do further tests tomorrow.
Regards, Ales On Thursday, March 7, 2013 11:34:23 AM UTC+1, Tim Richardson wrote: > > I have an app using the scheduler the old-fashioned way. I have a model > which sets up the scheduler. > myscheduler = Scheduler(db,dict(import_task_add=import_task_add)) > > The model also defines the task which the scheduler runs. > > However, the scheduling of a job is done by a controller, after the user > provides some job parameters. > Under the old approach, I start the job by inserting a record in table > db.scheduler_task > > Now, I want to use immediate=True which is not a column in the table; I > have to use scheduler_instance.queue_task > > and then in the controller I try > > result_ID=myscheduler.queue_task(import_task_add, > pvars='...'}, > immediate=True, timeout = 600) > > but it's silently failing. I don't get an entry in the scheduler tables. > Doing it in the controller is the least change starting from my current > code, but is this the wrong approach? > > > > -- --- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
