There are two aspects to this: the actual DB tables and the web2py mapping to the DB. The latter are stored in the .tables files in the database folder.
To keep the two in step, web2py automatically migrates the DB and updates the mapping from the models. To turn off that functionality (for production systems), each table's model can be set migrate=False. In your case, where the tables existing in the DB but the mapping is not up to date, you may set another attribute fake_migrate=True. Web2py will then update the mapping, but leave the DB unaffected -- which seems to be what you want. This information is available in the DAL chapter of the book. Regards, D On Mar 21, 2:24 pm, LarryEitel <larrywei...@gmail.com> wrote: > Thank you for the explanation and suggestion. My foray into web2py is > bearing fruit!
