View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016025 | MMW 5 | FileMonitor / Find Missing | public | 2019-10-08 12:04 | 2022-09-14 14:39 |
| Reporter | peke | Assigned To | |||
| Priority | normal | Severity | tweak | Reproducibility | always |
| Status | assigned | Resolution | reopened | ||
| Target Version | 5.2 | ||||
| Summary | 0016025: Manage Database: Rebuild and Optimize should remove Duplicate files | ||||
| Description | During Tests with user Database we have found that some DB tracks have duplicate IDs even they reference to same File (Path) We should make that Rebuild and/or Optimize remove such tracks by either Merging IDs to one or delete duplicates. Note: Same thing happen in MM4, but I am not sure it should be done due the possible risks User DB supplied on FTP. To find one of duplicate tracks search for "Pitbull" | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
I guess we can hardly auto-guess which of the duplicates should be deleted without a risk unwanted data loss. e.g. even the newer duplicates can have data like rating, last played, assignment to a playlist that can be important for a user. It must be up to user to decide which duplicate to delete. But at first case this should not happen at all, could be a script responsible for this? Ideally if you could find steps how to simulate the issue so that we could fix the cause and not just the consequence. |
|
|
I again suspect on Backup Script as user has used it in the past. That is why i suggested merge, but as you pointed they should be listed in Duplicate content and deletion of one should not remove other. I only occasionally see users with the problem and they usually contact me after it is progressed and after time pass ith a question hy Optimize database Full (MM4) didn't removed them and/or why Rebuild DB didn't fixed that (MM5) as they see to files playing even it is only one. |
|
|
So if I understand correctly, there are 2 possible approaches to fixing issues in which multiple entries point to a single file: 1) Automatically during DB optimization, by e.g. using the most recently edited entry 2) By ensuring that deletion actions only apply to the DB and do not delete such files (if a second entry points to the file) Personally, I think that the first approach is much better. Regardless, this is probably a low priority item. |
|
|
I believe that 0016162 was the cause - it has been already fixed so I guess there is no longer a need for remedy. |
|
|
Note that there must be also another cause in MM4, as user from ticket GFA-131-99765 attached MM4 database with these symptomps, solving via the ticket to find the cause... EDIT: Note that the duplicate files were not written by MM, but by a third party addon, because some of the columns in the Songs table have NULL value, MM always writes a value there. Finding more via GFA-131-99765 ... |
