migrate_enabled = false migrate = false fake_migrate = false fake_migrate_all = false
These settings are only if we don't need to update the database and use the current database. We can use these settings in the deploy mode. Am I correct? In other words, if I delete the entire database and reinstall the app, all these flags needs to be true. Isnt? What if in the case that we have a new table and we want to keep rest of the database intact? sought of in between. On Monday, September 5, 2016 at 11:25:12 AM UTC-4, Scott Hunter wrote: > > I found the problem; migrations weren't being disabled because, while I > had the correct settings in appconfig.ini, they were not being used > properly in creating the db object. > > - Scott > > On Saturday, September 3, 2016 at 1:01:39 PM UTC-4, Scott Hunter wrote: >> >> I have an app which runs *much* slower than expected on pythonanywhere. >> >> I enabled the profiler, and one thing stood out: on pythonanywhere, the >> function the most time was spent in, by far, is fcntl.flock from inside >> portalocker while loading the models. In fact, when run locally, >> portalocker isn't even being called: it goes straight from save_dbt to >> cPickle.dump. >> >> Is there some configuration specific to web2py that might address this, >> or is it something I should take up w/ the people at PA? >> >> - Scott >> > -- 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.
