collection-librarian should attempt to remove unneeded tracks, releases, albums, and artists

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

Bug Description

E.g., if a given artist has no associated albums and no associated tracks, then we should attempt to remove him from the database.

For the case of tracks -- at least, and perhaps for some other types -- we'll need to consider that the given track may have an association in the "track_suggestions" table. We ought to just catch and log any database errors that occur when attempting to remove such a track. In fact, we should catch all database errors when trying to remove any object.

Changed in resonate:
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Chris Wagner (chris-wagner) wrote :

It looks like unassociated artists were already being removed, actually; however, we weren't removing unassociated albums, so it's unlikely any artist would be removed in this way.

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

Addressed in revision 835.

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