songs.sqlite will not be downsized when deleting songs

Bug #636835 reported by rimach
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenLP
Fix Released
Low
Tim Bentley

Bug Description

Do the following steps for easy reproduction. (tested on windows)
1. rename songs.sqlite to songs.sqlite.orig
2. start openlp
3. import songs.sqlite.orig
4. close openlp
5. See in filemanager -> sizeof songs.sqlite
6. do the same steps 2-5 -> size of songs.sqlite is grown (thats correct)
7. start openlp
8. clean all double entries (because of they all existing twice after the second import)
9. close openlp
10. See in filemanager -> sizeof songs.sqlite => its the same size as step 6 (but, we have only the half of entries now???)

Related branches

Revision history for this message
rimach (crichter) wrote :

Oh I forgot:
11. After renaming the database from step 10, restarting OpenLP and import the database, we have the correct filesize from step 6

Changed in openlp:
importance: Undecided → Low
status: New → Confirmed
milestone: none → 1.9.4
Revision history for this message
Raoul Snyman (raoul-snyman) wrote :

This is the way SQLite works by design. We'll need to run the VACUUM command every now and then. I don't actually see the need for this, as disk space is cheap.

Changed in openlp:
assignee: nobody → Raoul Snyman (raoul-snyman)
Tim Bentley (trb143)
Changed in openlp:
assignee: Raoul Snyman (raoul-snyman) → Tim Bentley (trb143)
Tim Bentley (trb143)
Changed in openlp:
status: Confirmed → Fix Committed
Tim Bentley (trb143)
Changed in openlp:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.