When querying for an existing track, matching should be done on all relevant fields (artist_id, release_id, title, version, track_num, disc_num)

Bug #462073 reported by Chris Wagner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Resonate
Fix Committed
Medium
Chris Wagner

Bug Description

The problem is that if, for example, we have a previous entry that had an incorrect or no track_num present, but the file being processed now does have track-number information available, the database entry would not get updated appropriately.

Trying to actually update entries could lead to tricky situations where we might have one version of a release tagged incorrectly, conflicting with another version that is tagged appropriately. Rather than try to work out these situations, it would be better to simply have multiple entries in the 'tracks' table, cleaning out any unused ones at some point.

Revision history for this message
Chris Wagner (chris-wagner) wrote :

Addressed in revision 719.

Changed in resonate:
status: New → Fix Committed
Changed in resonate:
assignee: nobody → Chris Wagner (chris-wagner)
importance: Undecided → Medium
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.