BTW, what you are experiencing is totally predictable, but you're "barking 
at the wrong tree".

now:
migrate=True, fake_migrate=False

db.define_table('mi_tabla',    
    Field('f1', 'integer'),
    Field('f2', 'integer'),
    Field('f3', 'integer'),
    Field('f4', 'integer'),  
    migrate='mi_tabla.table'  
)

all is fine

now + 1:

db.define_table('mi_tabla',    
    Field('f1', 'integer'),
#    Field('f2', 'integer'),
    Field('f3', 'integer'),
    Field('f4', 'integer'),  
    migrate='mi_tabla.table'  
)

f2 is removed from the table

this exception "*ProgrammingError: column "f2" of relation "mi_tabla" does 
not exist"  *doesn't come from that model... you have some piece of code 
that is running and is referencing f2.

setting fake_migrate at this time doesn't do anything, as your table 
definition is already without f2 AND your "real" table hasn't an f2 column. 

-- 
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 web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to