Hey Alex, could it be that you define the table twice in the code?
Marin On Mon, Feb 8, 2016 at 6:56 AM, Alex Glaros <[email protected]> wrote: > If that model is consistent with the current state of the database, run > the code once with fake_migrate so web2py will update the migration > metadata. > > Well,, I forced it to be consistent with model by creating the field on > Postgres side. When ran fake_migrate, I received > column "reputation_comments" of relation "reputation" does not exist > > If that model is not consistent with the database, then delete the > relevant *.table file and run the code with a regular migration so web2py > will create any missing fields. > > To test in this situation, I deleted the file in the web2py databases > folder, and, dropped the table from the Postgres side. Ran migrate=True, > and for some reason it remembered the old table model, not the version with > the new field. It created the old table with no errors on the Postgres > side. Why would it remember the old model? I clearly saved the new model > version in db.py. > > > -- > 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. > -- 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.
