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, [email protected] <javascript:> > 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, >> you will never be able to use that new table's name for anything else >> because GAE doesn't offer access to a directory storing the *.table files. >> Any attempt to migrate after that will show the table doesn't exist (of >> course) and web2py will not attempt to create a table in SQL because it >> thinks it already exists. >> >> Unless there's some other way to delete the table files from GAE? >> >
-- 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.
