If instead of removing the field, create a new one, so does
db.define_table('mi_tabla',
Field('f1', 'integer'),
#Field('f2', 'integer'),
Field('f3', 'integer'),
Field('f4', 'integer'),
Field('f5', 'integer'),
migrate='mi_tabla.table'
)
First run, works fine, t
Second execution error occurs:
ProgrammingError: column "f5" of relation "mi_tabla" already exists
If the file sql.log we look, we see that for each request tries to create the
field:
timestamp: 2014-12-11T22:04:12.661919
ALTER TABLE mi_tabla ADD f5 INTEGER;
success!
timestamp: 2014-12-11T22:04:25.163228
ALTER TABLE mi_tabla ADD f5 INTEGER;
timestamp: 2014-12-11T22:09:39.553502
ALTER TABLE mi_tabla ADD f5 INTEGER;
timestamp: 2014-12-11T22:09:40.922113
ALTER TABLE mi_tabla ADD f5 INTEGER;
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
