On Wednesday, February 7, 2018 at 4:05:17 AM UTC-8, Leonel Câmara wrote: > > You are using fake migrate. It thinks it has migrated but it hasn't and > the column isn't on the DB. Remove the field in the table and do another > fake migration. Then put the field back and do a real migration. >
Ah, but the column IS in the database ... appadmin shows it clearly. The storage.sqlite file was copied from the working 2.14.6 environment. Copying the table files from there doesn't seem to help, BTW. The hash in the name is probably no longer matched. /dps -- 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.