Already tried it, did not worked (and just did, still not working).
Isn't it for modifying the table only, and not when creating a new
one ?

I mean, after deleting the table I wanted to change,
I thought it's normal for the "migrate=False,fake_migrate=True" not to
work, isn't it ?

On Aug 23, 5:22 pm, Richard Vézina <ml.richard.vez...@gmail.com>
wrote:
> set it :
>
> migrate=False,fake_migrate=True
>
> http://www.web2py.com/book/default/chapter/06?search=fake#Fixing-Brok...
>
> Then it F5 to refresh your page...
>
> It should correct your database schema... You can potentially lost
> data you have entered so, make sure you backup everything if important
> before doing that.
>
> Richard
>
>
>
>
>
>
>
> On Tue, Aug 23, 2011 at 11:17 AM, TomPliss <tompl...@gmail.com> wrote:
> > Hey (noob here again),
>
> > I needed to change the type of a field in my DB (the Date one of a
> > table was a string, i'm changing its require to IS_DATE).
> > but the values for existing entries were "wrong" (string has no
> > attribute year), so went on "oh, only tests are in this table, let's
> > drop it", and drop it in the sqlite I got, watching the DB.
>
> > So I get my DB, with a table not here.
> > I restart the web2py server, but the table still isn't here. I save
> > the model.py, restart (with the side sqlite off), still not here.
>
> > I checked in the book, chapter 06, "By default, migrate is set to
> > True". Isn't that what tells web2py to create the table, if it doesn't
> > exist ?
>
> > What am I missing ?

Reply via email to