Quote:
Originally Posted by Sefiriot
Another thing to report: this time on returning to the normal CC browsing screen with books, it was immediately usable, no sluggishness or failures to respond. Dare I suggest that when cleaning produces changes in the database, you would need to shut it down and reboot the app, but not if otherwise?
|
My guess is that if it is required in one situation then it should be done in the other, just to avoid problems. Closing and reopening the DB allows the system to clean up after itself, getting rid of journals and the like. Perhaps in this case there was nothing to clean up. Who knows...
I am going to look at what I need to do to auto-close/open the db. It should be easy given all the other robustness changes I made.