View Issue Details

IDProjectCategoryView StatusLast Update
0000802MMW v4DB/FileMonitorpublic2007-09-11 17:05
Reporterrusty Assigned To 
PrioritylowSeveritymajorReproducibilityalways
Status newResolutionopen 
Summary0000802: MM treats files as if in different locations when accessed via different paths to same location
DescriptionMM has problems when the user stores files (via the File Monitor or manually) in one node (e.g. /Location/Network/SharedMusic), but tries to access it via a different node (e.g. /Locations/C:/SharedMusic).

Possible solution:
-check whether edit is to file in the DB accessible via an alternate path
-if alternate path exists, then edit existing entry
-if alternate path doesn't exist, then edit current entry

--Jiri--
If I understand correctly, the only problem is that MM doesn't show files in local folders also in network folders and vice versa?

--Rusty--
Yes, and that when performing an operation on one, it isn't reflected in the other possibly causing duplicate entries.

e.g. add file to /Location/Shared Folder, edit it in /My Computer/Shared Folder --> duplicate entry appears if /My Computer/Shared Folder is being monitored.

--Jiri--
I never thought about solving this, because although both paths points to the same locations, they are from filesystem point of view different. This way we would have to take care e.g. of old DOS 'subst' command that can make an alias for a drive name. I don't think that this is something to be solved, in my opinion it's in users' responsibility

You mean that it doesn't work even when the paths are absolutely the same?

--Rust--
I half agree, but not completely. i.e. I agree with this when it comes to modifying the location of a file, but if the user attempts to edit an existing file that happens to have been added via a different path, MM should probably be smart enough to account for this.

The paths aren't identical: one is via C:/Shared Folder, the other is via /Network/Shared Folder

--Jiri--
I would have to review what does Windows API offer here, i.e. if there is any way how to implement it properly. However, in any case I don't see it as a necessity for this release, particularly because I'm not sure if there is an easy way of implementing this.

--Rusty--
I agree with you re. the urgency, however, people who use MM in a networked environment will undoubtedly face this bug.
Additional InformationProblem came up in user forum at:
http://www.songs-db.com/forum/viewtopic.php?p=2891
TagsNo tags attached.
Fixed in build

Activities

There are no notes attached to this issue.