Quote:
Originally Posted by dima_tr
Or trigger vacuuming as an additional script after each disconnect from PC, just after updating global.db. I agree, autovacuuming might not be a good idea.
|
I do not like the unpredictable duration of vacuum, how long does it take to vacuum a multi MB database file? So (at this moment) I am not in favour of doing it automatically.
Maybe some code in a Database-Settings-dialog that would be able to check the state of global.db and propose a vacuum to the user. An alternative would be to have such a functionality integrated in ctb.
On the other hand, we do not know which problem a vacuum would solve... does it improve performance or does it only cleanup some diskspace?