On Tuesday, November 28, 2017 at 9:37:38 PM UTC-8, mostwanted wrote: > > With some earlier versions of web2py, the APPS we created used to > experience *corrupt tables error* and back then we'd advised to put > migrate=False,fake_migrate=True > line before closing the table definition. > > My question is has this issues been addressed with the latest versions > like the 2.16.1 or are we still likely to get the *corrupt tables error *and > be forced to use the *fake_migrate* solution? > > Thanks > > Under what circumstances did you experience a corrupt tables error? I believe my only experiences with mangled table files involve Windows Update reboots or system crashes. I don't think I've had that problem on Linux machines. FWIW, I use the sqlite backend, although the table files are "front end".
/dps -- 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.
