This has happened to me twice in the last week on two different tables. I have started backing up the table files so that I can restore them. I will try to use fake_migrate next time.
Is there any way to avoid having this happen in the first place? Thanks! Jeff On Sep 1, 10:55 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > yes. db.define_table(...,fake_migrate=True) > > On Sep 1, 12:11 pm, vince <lapcc...@gmail.com> wrote: > > > > > upgraded to 1.83.2, the application itself run fine just with this > > error appearing in error log sometimes. > > > is there any way to regenerate the db table file? > > > Traceback (most recent call last): > > File "gluon/restricted.py", line 186, in restricted > > exec ccode in environment > > File "/home/web2py/applications/cms/models/db.py", line 36, in > > <module> > > auth.define_tables() # creates all needed > > tables > > File "gluon/tools.py", line 1153, in define_tables > > self.settings.table_membership_name, migrate)) > > File "gluon/sql.py", line 1359, in define_table > > t._create(migrate=migrate, fake_migrate=fake_migrate) > > File "gluon/sql.py", line 1839, in _create > > raise RuntimeError, 'File %s appears corrupted' % self._dbt > > RuntimeError: File /home/web2py/applications/cms/databases/ > > fb87181b96a99be45f5a23f4277867ce_auth_membership.table appears > > corrupted
