I agree. define_tables needs a migrate=True/False option. Massimo
On Mar 3, 8:28 am, AchipA <[email protected]> wrote: > ... also, this means that you cannot use the same user database across > multiple nodes/web2py installs (bad, bad, bad). Unless you override > define_tables, but I don't think that's a long term alternative. > > On Mar 2, 6:29 pm, AchipA <[email protected]> wrote: > > > A small problem popped up on upgrade to 1.57. Apparently something > > changed in gluon/tools.py and web2py wanted to try a migrate, but it > > failed miserably. Checking mysql logs show. > > > ALTER TABLE auth_user ADD first_name__tmp VARCHAR(128); > > UPDATE auth_user SET first_name__tmp=first_name; > > ALTER TABLE auth_user DROP COLUMN first_name; > > ALTER TABLE auth_user ADD first_name VARCHAR(128); > > UPDATE auth_user SET first_name=first_name__tmp; > > ALTER TABLE auth_user DROP COLUMN first_name__tmp > > > after this statement I get the 'commands out of sync' statement. If I > > just go back to the previous revision of gluon.tools it works again. > > Is there a way to make the tables generated/used by gluon/tools.py > > make a bit more (non)migration friendly ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
