build 1656 UpdateDb after change path add track to lib

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: build 1656 UpdateDb after change path add track to lib

Re: build 1656 UpdateDb after change path add track to lib

by uziubalmy » Mon Sep 16, 2013 5:25 am

I think that zvezdan is right, it was strange that "Path" didn't need UpdateDb, but this isn't absolutly a problem. My opinion is just that using the "path" property for move o rename a file that is not in library shouldn't add nothing to the db. With UpdateDb or not for me it's not important. However, thanks for the support, you are greats.

Re: build 1656 UpdateDb after change path add track to lib

by Ludek » Mon Sep 16, 2013 4:58 am

Hi, this was changed per Zvezdan request here: http://www.ventismedia.com/mantis/view.php?id=11121

But you seem to be right that the old behaviour was probably better, going to revert (also for the reasons to not break compatibility with old MM scripts/addons).

Reverted in build 1659.

build 1656 UpdateDb after change path add track to lib

by uziubalmy » Thu Sep 12, 2013 4:43 am

I'm using the buil 1656.

From this or the previous build i must use UpdateDb method after changing the path of a sdbsongdata object for move o rename it. Before I didn't need to use updatedb.

But this is not a problem.

The problem is that now if the track is not in the library it will added automatically. And then, if the new path is in a library folder, when the scan runs, it will added twice. This is a bug... i don't know. But when i want to move a file changing the path property and this file is not in the library why it must be added to the library? this is wrong. I move thousands of file with the MM apis before put them into the library folder and this is a disaster for me becouse now I have thousands of dubplicate tracks.

Please return to the previuos behavior. This is illogical.

Top