I'm not sure if this is different with sqlite but with postgres and mysql, you would do the following: 1) delete all the .table files in the databases directory 2) set migrate=True and fake_migrate=True (also make sure lazy_tables is False) 3) start your app with the scheduler option enabled. You should see the new .table files created for all tables in the db, including the scheduler. 4) shutdown your app and now you can set migrate=False (avoid any unplanned table changes) and lazy_tables=True. Now restart your app and it *should* work as expected.
This is how I moved quite a few of my apps between servers (all on postgres though - but I imagine it works the same with sqlite). More info: http://web2py.com/books/default/chapter/29/06/the-database-abstraction-layer?search=fake_migrate#table_migrations HTH, On Sunday, 18 October 2020 at 00:54:53 UTC+1 Ramos wrote: > Hello i moved my app to opalstack from webfaction. > I have a sqlite db. I deleted all files inside databases folder with > .table extension and changed dal connection to > migrate=False,fake_migrate=False > all is ok now but i cant start scheduler. > I went to app admin and got the same error. > I noticed that .table files are created in databases folder for > scheduler_* tables > > any help? > thank you > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/77e16951-7284-4777-904a-7904ef24c2edn%40googlegroups.com.
