I believe web2py probably thought the field already existed. It most likely had an entry in the .table files that it had created this one before.
-Thadeus On Mon, Dec 7, 2009 at 12:12 PM, Wes James <[email protected]> wrote: > A temp fix for this was to just add the field in the DB. Isn't web2py > supposed to do this though? > > -wes > > On Mon, Dec 7, 2009 at 10:57 AM, Wes James <[email protected]> wrote: >> I added a field to db.py and did some tests. I then went back to the >> previous sqlite.db that did not have the new field, now I get a field >> does not exist since the databases/....table file has the field, but >> the db does not. How do I get web2py to create the field again? I >> tried migrate=True, that is True by default isn't it? >> > > -- > > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/web2py?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
