See the book, chapter 6 fixing broken migration. Here is an excerpt, good luck:
The solution consists of disabling migrations for all tables and enabling fake migrations: db.define_table(....,migrate=False,fake_migrate=True) This will rebuild web2py metadata about the table according to the table definition. Try multiple table definitions to see which one works (the one before the failed migration and the one after the failed migration). Once successful remove the fake_migrate=True attribute. Before attempting to fix migration problems it is prudent to make a copy of "applications/yourapp/databases/*.table" files. On Mar 13, 10:08 pm, VP <vtp2...@gmail.com> wrote: > Well, I tried to modify my model by changing a column. I am using > postgres. That apparently messed things up. Setting migration to > True does not work. > > Viewing the database using psql, I saw that that column was deleted, > but adding the same field (in web2py) does not recreate that column. > Is this a glitch with web2py's migration? Or am I doing something > wrong? > > Please help as my app is currently not usable.
