Thanks, all. This is closed. I am progressing to more deployment complexity: locally develop on xampp with apache and mysql; occasionally run rocket/sqlite if I can't figure things out move things to SuSE server in my office and access behind firewall on own network move things to Linode (probably Centos) after they really, really work!
Slowly but surely I am getting to understand this. Deployment still seems the biggest bug-a-boo. On Jan 15, 12:51 pm, Massimo Di Pierro <massimo.dipie...@gmail.com> wrote: > +1 > > On Jan 15, 1:21 am, pbreit <pbreitenb...@gmail.com> wrote: > > > > > > > > > Migrations are pretty powerful but problems can arise. As I've suggested > > elsewhere, best to develop against SQLite and then deploy as desired. In > > development, I change models frequently. If I run into a problem that I > > can't fix with migrations, I might delete the whole database folder and > > start over. That's simple with SQLite. > > > The sql.log is just a log. I think web2py compares the .table files to the > > database to figure out what needs to be migrated. > > > I think fake_migrate rebuilds the .table files according to the model files > > without touching the DB. > > > There's probably room for improvement in the documentation, especially > > around fixing broken migrations, what the files are in the database folder > > and what migrate/fake_migrate actually do.
