don't know how to reply "properly" .... the scheduler in "stable" has some column names that are incompatible with check_reserved=['all']. If you have a db connection with check_reserved=['all'] there's no way to have a working scheduler in your app. The solution is either rely on the stable scheduler and leave out the check_reserved parameter or use the scheduler from trunk.
Table migrations are handled like everything else in web2py, so there's no change in that behaviour regarding the update. On Sunday, February 17, 2013 3:49:27 PM UTC+1, MJo wrote: > > > > What is the most elegant way to upgrade web2py? Upgrading core is easy but > how to deal stuff inside one particular application? Now I utilized > BeyondCompare3 to sync all those Twitter Bootstrap and so on stuff. > > Considering this Scheduler table problem, can I some how drop all affected > tables and get new ones automatically created? Trying to stay up to date > with latest released version, not wanting anything from the trunk. > -- --- 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.
