PATCH: Unexpected behavior when exaile accidentally gets duplicate items in the DB

Bug #884074 reported by Dustin Spicuzza
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Exaile
Fix Released
Medium
Dustin Spicuzza

Bug Description

If, for some reason, exaile accidentally writes two identical entries to the track database, it will fail to load any data that is saved after that point, and will always load the older track data from the DB, while saving to the newest track data entry in the DB.

My fix elects to use the first (probably older) entry found in the DB, since the other entry happened because of some kind of error. It's also not clear what the ramifications of multiple track databases would be -- but I think this still does the right thing.

I did not try to determine what caused the DB to be corrupted, I presume that it happened during plugin development.

I've pushed this change to my dj_improvements branch also.

Tags: patch

Related branches

Revision history for this message
Dustin Spicuzza (dustin-virtualroadside) wrote :
Mathias Brodala (mathbr)
Changed in exaile:
assignee: nobody → Dustin Spicuzza (dustin-virtualroadside)
importance: Undecided → Medium
milestone: none → 0.3.3.0
status: New → Fix Committed
Changed in exaile:
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.