Large prompt.db file and Error vacuuming database: database or disk is full

[VladanZ]

Dear all, I just found out that my prompt.db size is 7GB because it fully filled my drive while performing maintenance on database leading to not enough space error and full computer crash.

Is there a way NOT to store binary data (images, thumbnails) inside the database and store only text prompts + text metadata while still be able to use Gallery feature?

I use PromptManager v1.

[vitosans]

The current version (v3.0.21) of PromptManager does NOT store binary image data or thumbnails in the database. The database schema only stores:

prompts table:

• Text prompts and metadata (category, tags, rating, notes, hash)

generated_images table:

• image_path (TEXT) - File path only, not binary
• filename (TEXT)
• workflow_data (TEXT) - JSON metadata
• prompt_metadata (TEXT) - JSON metadata
• parameters (TEXT) - JSON metadata

The gallery system works by storing file paths and reading images from disk on-demand, not by storing image binaries in the database.

Likely Causes of 7GB Database

Given you're using v1, here are the probable causes:

1. SQLite Bloat from Many Operations: Frequent inserts/updates/deletes without VACUUM can cause significant database bloat
2. Duplicate Prompts: Before the deduplication system was robust, many duplicates may have been stored
3. Large JSON Metadata: Extensive workflow_data JSON being stored for each image
4. No Maintenance: Database fragmentation over time

[VladanZ]

Thank you!
I wrongly presumed binary data are stored due to databaze size. I was able to free drive space for both VACUUM and prompt deduplication to finish successfully which decreased the databaze file size almost 10x to 800 MB.