yep, that's definitely the case. when scheduler gets a new feature, it's possible that the underlying table get changed. as table definitions are inside scheduler's code, you need to let migrations happen (or even better, drop the scheduler_* tables on the backend, drop related .table files, and let them be recreated) to make it work.
On Monday, February 29, 2016 at 8:56:31 PM UTC+1, Dave S wrote: > > > > On Monday, February 29, 2016 at 9:06:03 AM UTC-8, peter wrote: >> >> I have upgraded to web2py version 2.13.4 from 2.8.2 >> >> When I use the scheduler I get. >> >> OperationalError: table scheduler_task has no column named prevent_drift >> >> >> Any suggestions? >> >> Thanks >> >> Peter >> >> > > I think one of Niphlod's standard recommendations may apply: Turn > migrations on (DAL string in models/db.py), access your appadmin page, and > then turn migrations off. (Access can mean browser or wget or curl ... the > URL path is the important part (and appadmin is convenient), to insure that > models get read). > > Your tables might not have changed, but the scheduler was upgraded 18 > months ago, and that may have involved its tables. > > /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.
