View Single Post
Old 04-05-2017, 04:23 PM   #6
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,796
Karma: 30237628
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by kovidgoyal View Post
It doesn't. You want to vacuum the db from the command line, just do:

calibre-debug -c "from calibre.library import db; db().new_api.vacuum()"
Not the answer I anticipated, I've always assumed it was same as Library Maintenance. Good job I checked I was going to suggest to someone they could use the calibredb check library command to do the vacuuming

Quote:
Originally Posted by kovidgoyal View Post
Yeah -- sorry I forgot to post here. https://github.com/kovidgoyal/calibr...693b245f37c078
So do I need to add calibre-debug lines to to my weekly housekeeping script, or will the next version of calibredb check-library do it for me?

Might as well ask: does calibredb check-library do the database integrity check (the step between the vacuum and the consistency check in the GUI version) ? If not could it?

BR
BetterRed is online now   Reply With Quote