Mine has exceeded 1 GB, a real challenge, for backups e.g. and space in general.
I had proposed long time ago to support a second "archive" track DB, that may reside on ext. SD e.g. and will be part of searches, but not part of backups (you do that once to an offline device like OTG USB drive or a PC).
That mechanics should of course include the pruning of the original DB (your point in the post).
I had proposed long time ago to support a second "archive" track DB, that may reside on ext. SD e.g. and will be part of searches, but not part of backups (you do that once to an offline device like OTG USB drive or a PC).
That mechanics should of course include the pruning of the original DB (your point in the post).