if it exist already you don't need .table at all. just set migrate=False. .table files are web2py way of tracking what is supposed to be already in the database for two reasons: - if you define a table that doesn't exist, create it - if you changed the definition of a table (e.g. added a field), adjust what is yet in db to match the current model
web2py doesn't do introspection automatically (doesn't know ANYTHING about what is in the database already) and doesn't want to. You either start "fresh" with no .table and let migrate=True work (default behaviour) or you start with something in it and set migrate=False to turn off the entire machinery. It's not all black or white, though. The "grey" consinst in you defining a model for all existing tables (i.e. migrating an app TO web2py, with a yet-existing database) and start "fresh" by setting migrate=True and fake_migrate_all=True, with the latter turned on just for a single request. In that single request, web2py will re-create .table files from your current model. Later on, when you'll alter that definition, it'll keep your database tables in sync with your model. -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
