I had a db for which I changed the model. This correctly caused a migration. Either web2py or MySQL hung. This has sort of diminished my confidence in migrations. I realize it is a great thing, but only if/when it works. Believe me I am experimenting with a really trivial example with 3 tables (plus auth) and about 3-4 fields each with about as many rows of test data. So, if it hangs for this...
Anyway, I manually purged the tmp column and make sure the data was ok. Set the table in question to migrate = False. All worked ok. Terrific. With things working I decided I would put the model back the way it was originally and removed migrate = False from the offending table. Then, when I ran the app--web2py attempted a migration. There must be something like the data-time stamp of the model compared to some inner value that triggers the migration. Is there someway I can get the inner state in sync so the migration doesn't happen? I sent another post about what went wrong with the migration itself. Now I am just trying to get everything cleaned up manually. Many thanks.
