.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. Mirek Dne čtvrtek, 16. října 2014 1:10:07 UTC+2 Yi Liu napsal(a): > > Dear all, > > I am trying to backup my sqlite databases using its backup API: > sqlite3 storage.db ".backup db.bak" > > I noticed it made a copy of storage.db. But how about all those .tables > files. I search about sqlite and web2py, seems nothing came up about them. > > Using ls -l, I can tell most these .table files have not been modified for > a long time. So no data is in them. > > Should I back up them or not? > > Thanks! > > -- Yi > > -- 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.
