Keep xklb-metadata.db when doing manual testing

[deldesir]

Testing changes to IIAB Calibre-Web requires starting with a fresh database instead of keeping/using the existing /library/calibre-web/xklb-metadata.db. The process would involve to:

1. Remove the database with rm -f /library/calibre-web/xklb-metadata.db.
2. Restart Calibre-Web to regenerate xklb-metadata.db automatically by xklb (or SQLAlchemy if the refactoring changes are applied) when submitting a new video to download.

However, this approach has become cumbersome, especially as the database grows with important data or if specific data needs to be selectively modified rather than fully reset. Removing the entire database is overkill then when only one or a few rows need to be removed for testing purposes.

Proposed Workaround

Instead of removing the entire database, a more targeted approach can be used with lb search-db.

Steps:

1. Delete the affected row:

   lb search-db /library/calibre-web/xklb-metadata.db media <video_URL> --delete-rows

2. Submit the video again via the "Download to IIAB" button in the web UI.

This approach helps to avoid unnecessary deletion and regeneration of xklb-metadata.db.

[holta]

Proposed Workaround

Instead of removing the entire database, a more targeted approach can be used with lb search-db.

Steps:

1. Delete the affected rows:

   lb search-db /library/calibre-web/xklb-metadata.db media <video_URL> --delete-rows

2. Submit the video again via the "Download to IIAB" button in the web UI.

• @deldesir is this new approach ready to be promoted to testing volunteers?

• Can you mention other/relevant Test Plan(s) (or future testing scenarios) where this will help, if possible?

Thanks!