nope. you have to delete the corresponding .table file from the databases/ folder. web2py doesn't do "introspection" of a database.
It stores in the .table files what it thinks the database actually looks like, and compares .table contents to what models are, eventually triggering a migration. (that's why in production you'd like to DISABLE migrations.... so web2py doesn't have to compare at every request your model with the .table files) if the .table file is not found, the corresponding table is assumed to not exist in the underlying database, so a creation is triggered. sql.log is **only** meant to see what DDL statements are issued to the backend. On Wednesday, November 27, 2013 10:08:27 PM UTC+1, 黄祥 wrote: > > had you define migrate=True on your models and delete sql.log on your > databases folder? > > best regards, > stifan > -- 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.
