On Thursday, November 30, 2017 at 1:40:05 AM UTC+2, Dave S wrote: > > > > 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 > > Hey Dave, it was just a random error really, i'd work on an projec, shut > my machine, the next time i re-opened the project and tried to make a > database entry i'd get the error!! > But now that u are mentioning system crushes maybe it had something to do with my hard-drive coz it always gave me problems since i last dropped my laptop, maybe those errors stemmed from that. All along i though it could be a bug that came with the version of the web2py i was using, i posed this question to be sure coz lately i've been working on clients projects and feared that may still be an issue with web2py!
-- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
