I experienced the same error simply changing the MySQL user's password. I was able to get around it by setting migrate=False on every define_table call on my model.
On Aug 20, 10:10 am, Fred <fre...@gmail.com> wrote: > I ended up doing this: > > Create empty database on new server. > Change db.py to connect to that new database. > Visit an application page in the browser; web2py creates the > application tables in the database, empty. > Dump the data from the oldMySQLserver with --no-create-info option > (notablecreation DDL). > Load that dumped data into the newMySQLserver. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
