You have both migrate and fake_migrate True at the same time? The intent of
fake_migrate is to sync an unsynchronise model/DB and it should be use in
conjonction with migrate False...
May your issue coming from there?
Richard#
On Mon, May 25, 2015 at 3:50 PM, Niphlod wrote:
>
> If you changed
If you changed the model, forms should reflect the changes istantly
can you post your before and after model ?
PS: beware of sqlite gotchas
http://web2py.com/books/default/chapter/29/06/the-database-abstraction-layer#SQLite
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documenta
Thank you for your atention Richard.
Initially there was no migrate setting for the table, then realizing not
working i tried to set explicitly migrate=True and then fake_migrate=True.
However i don't think is there the problem, due to the fact that web2py has
indeed created the column in the db,
What the state of your migrate flag? True or False?
Notice there is also a migrate_all or something at the DB string level
which prevent migrating of every tables...
Richard
On Mon, May 25, 2015 at 11:48 AM, goome wrote:
> Hello
> i again here to beg your help.
> I modified a table (adding a c
Hello
i again here to beg your help.
I modified a table (adding a column and setting writable=False in another)
in modes/db.py
but it had no effect: nor a form created by SQLFORM reflect the changes,
nor
db.table.fields show the new column.
But the column has indeed created in the db (sqlite). I
5 matches
Mail list logo
