Niphlod, yes, that was it !! It was not in the db.py but there was a 0.py with 'settings.migrate = True' (this is not my app, I was just asked to hack there to fix an issue).
An easy workaround might be to also set fake_migrations to True (fake_migrate_all=True in DAL() creation) and copy and execute the proper statements from databases/sql.log. That's what I did because just turning that settings.migrate into True brought me issues with tables already existing. I was digging in this half a day. An idea: showing the migration status of the app somewhere in the header of the database admin page. Huge thanks again for your great help! Yassen On Thursday, December 5, 2013 11:53:43 PM UTC+2, Niphlod wrote: > > check for > db = DAL(....migrate_enabled=False) > > either this prevented the creation of the table, or some another > migrate-related glitch. > To create scheduler's tables, you just need to do (as you did) > > Scheduler(db, ...) > -- 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/groups/opt_out.
