> First, drop the row. > Second, add the row again with the new size
Yes, this resulted in a migrated table with the new field having the correct size and no errors. (obviously I lost the data in the field). I can't see how the migrate commands written in sql.log are different from when I hand- migrated using the same commands. Does the python db interface layer wrap the web2py's query with anything? > > > I made a change to one of my models to increase > > the size of a VARCHAR field from 64 to 138. I'm > > using MySQL 5.0.51a-3ubuntu5.4 and web2py 1.57. I > > had the same problem with web2py 1.55. > ... > > The error I get is: > > File "[...] web2py/gluon/main.py", line 368, in wsgibase > > SQLDB.close_all_instances(SQLDB.rollback) > > File "[...] web2py/gluon/sql.py", line 504, in close_all_instances > > action(instance) > > File "[...] web2py/gluon/sql.py", line 873, in rollback > > self._connection.rollback() > > ProgrammingError: (2014, "Commands out of sync; you can't run this > > command now") > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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 -~----------~----~----~----~------~----~------~--~---
