migration type mismatch

[goome]

from the book :"define_table checks whether or not the corresponding table exists. If it does not, it generates the SQL to create it and executes the SQL. If the table does exist but differs from the one being defined, it generates the SQL to alter the table and executes it. If a field has changed type but not name, it will try to convert the data"

So  i suppose that this could help me in cleaning data (from type mismatch).

i copied the current project(application) in a new one, leaving in the dir 'databases' only the sqlite storage.

But when i open the home page od this copied app, i got 'table already exists'.

In models/db.py there are no migrate setting , except for auth table, where i set it to migrate=False, as this seems necessary.

Why web2py does not alter(if needed) the table, and instead complains of already existing one?

[Anthony]

You didn't turn off migrations in the new app, so web2py thinks it needs to create the table. If you want the new app to control the migrations, you'll have to run one fake migrate so the new app will have a record of the current state of the database.

Anthony

[goome]

Thank you very much for your help. Sadly, it did not work.

[Anthony]

Hard to say without knowing more details of the code, the content in the database, etc.