2.15.3-2017.08.07 I had same here, with SQLite too.
I confirm it can be solved so: 1) rename databases/ to databases_corrupted/ 2) create empty folder databases/ 3) navigate to appadmin or main page -> database is now empty 4) copy databases_corrupted/sqlite.db back to databases/sqlite.db or so: 1) remove databases/*.table metadata 2) in models in db=DAL() temporary add db=DAL(..., fake_migrate_all=True) 3) navigate to appadmin or main page -> database is now empty 4) remove fake_migrate_all=True from source code However in my case this is a localhost copy (localhost backup) of production database. There is no problem in production, but when I copy sqlite.db from production to localhost, I will receive "insecure string pickle" again. Can it be some cross-versions problem of some library, between production and localhost? Dne pátek 4. srpna 2017 18:15:29 UTC+2 Leonel Câmara napsal(a): > > This is weird I would just move all table files to a backup migration and > do a fake migration to recreate them and see if it solves the problem. > -- 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.
