Normal
If I understand correctly that would be my solution #2.As you mentioned it will only work if the path is already in the db. Not good. Add it if it isn't in.You update the pathID for every file each time you browse a folder....not good because it will be slow (and unnessarily so). Doing it while browsing a folder with 200 items will probably kill performace. Why don't you add a few lines of code into the imdb lookup code, so if you move a file you can simply do a lookup again, but if your new code detecs the filename already in the db it will simply update (or insert) the path and not do the actual lookup again. In this case you could add a question to he user "A file with the same filename is already in the Database. Did you move this file?" This way it will work for users with several files with the same name but will also be simple and fast for users who move their files around.It will require some user interaction, but IMHO it would be better and it will not remove functionality for other users.
If I understand correctly that would be my solution #2.
As you mentioned it will only work if the path is already in the db. Not good. Add it if it isn't in.
You update the pathID for every file each time you browse a folder....not good because it will be slow (and unnessarily so). Doing it while browsing a folder with 200 items will probably kill performace. Why don't you add a few lines of code into the imdb lookup code, so if you move a file you can simply do a lookup again, but if your new code detecs the filename already in the db it will simply update (or insert) the path and not do the actual lookup again. In this case you could add a question to he user "A file with the same filename is already in the Database. Did you move this file?" This way it will work for users with several files with the same name but will also be simple and fast for users who move their files around.
It will require some user interaction, but IMHO it would be better and it will not remove functionality for other users.
