I'm pretty sure I tried that as well without success... However, the problem is solved now. Something was wrong with the databases files (or I was missing something) and also I had comiled files that was recreating this field whenever I tried to remove it. My solution was perhaps not so pretty but here is what I did:
Reverted to version without the field, removed everything in the databases folder (kept backups), removed the compiled folder, backed up and dropped the database then created it again, set migrate=True and started up the app, imported the database dump, and finally, updated the app to the version having the new field. Now everything works, and hopefully I will not have these problem next time. Thanks for your input! Regards On Tuesday, February 7, 2017 at 7:17:28 PM UTC+1, Leonel Câmara wrote: > > Using the old version without the column you need both migrate=True and > fake_migrate=True to rebuild the table files. > > Then add the new field and fake_migrate=False. > -- 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.
