The simple stuff you talk about should simply work:

0. backup the database, this is just good practice...
1. if you're running the scheduler you should stop it until migration is 
finished and migrate is disabled
2. update the code making sure migrate is True.
3. visit appadmin to make sure all tables migrated even if they're lazy
4. disable migrations
5. restart scheduler

We should probably have a command line to do 2,3 and 4...

-- 
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.

Reply via email to