Opened 20 years ago
Closed 20 years ago
#950 closed defect (fixed)
Mythmusic clears song rating during 'Scan for New Music'
Reported by: | Owned by: | Isaac Richards | |
---|---|---|---|
Priority: | minor | Milestone: | 0.19 |
Component: | mythmusic | Version: | 0.18.1 |
Severity: | low | Keywords: | rating music track scan |
Cc: | Ticket locked: | no |
Description
During a Scan for New Music if any files appear to have 'changed' mythmusic puts the latest metadata into the music database, unfortunately this also erases the current songs Rating (as this is not stored in the id3tags but is part of the metadata structure). Fortunately Playcount is not affected by the Metadata::updateDatabase call.
Although a minor defect, (its only ratings, and only on files that have been changed - typically id3 tags updated), it does cause _all_ ratings to be lost on an upgrade from 0.18 to the latest SVN, so would be worth fixing before the next release.
Attachments (1)
Change History (3)
by , 20 years ago
Attachment: | rating.diff added |
---|
comment:1 by , 20 years ago
Noticed that the lastplay TIMESTAMP field is updated on every update to the track details, not sure if this is because I'm using MySQL 4.0.* or whether it should really be a DATETIME field instead?
Patch to address rating item only, more generic fix would be better, tested ok.