View Single Post
Old 02-03-2018, 07:26 PM   #3
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,104
Karma: 60406498
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by BetterRed View Post
Relational databases accumulate dross over time, mainly due to deletions and replacements, so they need to be optimised occasionally - aka as 'vacuuming' Ψ²

By rebuilding it you have eliminated the dross. FYI - the Check database function does a 'vacuum' as its first step.

BR
I agree with all you said. But...

not the 4 times bigger part.
Everything (in the defining tables) would have to have been redefined, many times to get that huge.

I DO recommend 'quarterly' housekeeping (Calibre Maintenance) on any Library with frequent Metadata defining changes. FWIW in a RDB you define an Author: J.D. Robb. You assign that defined author INDEX (not visible to a normal user) to a book entry. , The same is true for all column types except Comments. That is a BLOB.
theducks is offline   Reply With Quote