View Single Post
Old Yesterday, 11:08 PM   #5
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 53,344
Karma: 181495311
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Loosheesh View Post

For the Audit Log, what does the developer mean by "You should then vacuum/compress this Library using menu path Library > Library Maintenance > Check Library." (I reattached the developer's image for easy reference.)

Why must I do this, and what will happen if I don't? Will the plugin not work? Will doing it have other effects on my library? Also, should I go with all three 'compact' options?
Vacuuming a SQLite database compressed it by removing unused entries. If you are not an annotations user, you can skip that item. Though personally, I use all three of them. Especially on my Intake library, the FTS database has a lot of unused entries since after metadata updates and editing, the books are moved to my Main library.
DNSB is offline   Reply With Quote