See Anthony's original answer to this question. All you should need to do is remove the associated *.table files from the /databases folder. Also, make sure you have migrations turned on by setting migrate=True in you DAL() setup.
-Jim On Monday, January 22, 2018 at 6:06:10 PM UTC-6, SR wrote: > > How do we recreate the auth tables after it has been dropped in mysql > database? > I would really appreciate your help. > > On Monday, November 25, 2013 at 8:34:18 PM UTC-6, Anthony wrote: >> >> web2py thinks it already created those tables (you dropped them outside >> of web2py, so it doesn't know they're gone). Try removing the associate >> *.table files in the /databases folder (they store the migration >> information for each table). >> >> Anthony >> >> On Monday, November 25, 2013 9:22:58 PM UTC-5, Julien Courteau wrote: >>> >>> (a) I did: drop table <auth tables>; <auth tables> == ["auth_user", >>> "auth_group", etc...] in a sqlite3 shell; >>> >>> (b) I refresh my index page: web2py execute the auth.define_table() >>> silently but no tables had been >>> created (sql.log contains no create table). I tried to figure out what's >>> happening without success. >>> It did the same if I create a fresh new app. I use web2py 2.5.1. Any >>> clues? How Could I do to figure >>> out the problem? >>> Thanks. >>> >> -- 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.
