On Thursday, October 16, 2014 1:03:00 AM UTC-7, Mirek Zvolský wrote: > > .table file will change only, when you change table definition (usually > defined in model like db.py). > So if you decide to backup them, you can reuse them later, if they relate > to the same (not changed) table structure as is in your database backup. > > I use simple small application at alwaysdata hosting and I backup these > .table files. Sometimes (2 or 3 times in year) something go wrong, sqlite > database was never corrupted, but one of these .table files usually was > (regardless that they don't change). So I copy the corrupted .table file > back from my backup (its name I know from error ticket) and always was then > all ok. > > Looking at Leonel's comment, isn't it just as easy to delete the offending .table file and do a fake migration to recreate it? And wouldn't this help avoid using a backup that's a little too old, and has the wrong schema?
/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.
