This is known (rare) problem with mysql. Mysql cannot perform multiple alter tables in one transactions. It needs to be committed at each alter table. So it may happens that when you try con change type of a file between incompatible types, it fails in between and some of the temp steps have already been committed.
The only option is manually remove the unwanted table from the database. This is a very rare condition. Yet, to me this itself is a good reason to use postgresql. Massimo On Jan 31, 2:06 pm, weheh <[email protected]> wrote: > OK, so I took the code that runs on my development machine and tried > it out on my server. Now, on the server, I get a ticket that I don't > get on my development machine: > > 2.3.4.5.6.7.8.9.10.11. Traceback (most recent call last): > File "gluon/restricted.py", line 173, in restricted > File "D:/web2py/applications/myapp/models/1_tables.py", line 156, in > <module> > File "gluon/sql.py", line 1252, in define_table > File "gluon/sql.py", line 1709, in _create > File "gluon/sql.py", line 1763, in _migrate > File "gluon/sql.py", line 923, in <lambda> > File "MySQLdb\cursors.pyc", line 166, in execute > File "MySQLdb\connections.pyc", line 35, in defaulterrorhandler > OperationalError: (1060, "Duplicate column name 'assignment__tmp'") > > 1_tables.py is obviously where my tables are defined. Thoughts? -- You received this message because you are subscribed to the Google Groups "web2py-users" 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.
