Given that it's a field that is used just for internal usage, the default is "now", and it's used later on for: - repeating tasks - pop out from the queue the tasks in the correct order - mark a task as expired
Given the second point, the current default fits the bill, and BTW, users should never see next_run_time if start_time is greater . On Monday, May 12, 2014 12:30:43 PM UTC+2, Tom Clerckx wrote: > > Hi, > > When adding a new task via queue_task, the next_run_time is initially set > to the time the task is added to the queue. Is there a specific reason for > this and is there a way to set the first_run_time correctly immediately > when adding a new task to the queue? > I would expect that the first_run_time would be initialized to the > start_time of the task. > > The problem is that if I show the queue in a grid, from a user > perspective, the initial next_run_time of a created task seems to be in the > past which may create confusion. > > Only after the time the task has actually ran for the first time, the > next_run_time field is properly updated. > > > My web2py version. > Version > > 2.8.2-stable+timestamp.2013.11.28.13.54.07 > (Running on Rocket 1.2.6, Python 2.7.5) > > Best regards, > Tom. > -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
