[web2py] Re: fake_migrate bug on GAE

2016-07-29 Thread webmaster
Done. On Friday, July 29, 2016 at 6:26:49 AM UTC-7, Massimo Di Pierro wrote: > > Can you please open an issue? > > On Thursday, 28 July 2016 03:33:01 UTC-5, webm...@trytha.com > wrote: >> >> I realize this was a foolish mistake, but there really should be a way to >> fix it, and I believe there

[web2py] Re: fake_migrate bug on GAE

2016-07-29 Thread Massimo Di Pierro
Can you please open an issue? On Thursday, 28 July 2016 03:33:01 UTC-5, webmas...@trytha.com wrote: > > I realize this was a foolish mistake, but there really should be a way to > fix it, and I believe there is not. > > If you have fake_migrate=True and define a new table, then push to GAE, > yo

[web2py] Re: fake_migrate bug on GAE

2016-07-28 Thread webmaster
In case someone runs across this, the only solution I've found is to set up an IPv4 connection to your Cloud SQL and connect from your local machine. Then delete the ".table" entries corresponding to the pertinent tables from the web2py_filesystem table in your DB and run a regular migrate. On