Maybe it's OK for this query to fail (assuming this fails due to violating the UNIQUE table constraint).
For example, what if we relocated a folder to a folder that is already in the folder list? We wouldn't want to bail out of this function before relocating all their tracks because presumably they have moved all the tracks in the oldFolder to newFolder and wanted the Mixxx library rows to be updated for those tracks even though newFolder is already a Mixxx library folder.


What if the user moves all their tracks from folder A to folder B and folder B is already in their Mixxx folder list. When they hit relocate in Mixxx, we will bail out here and not relocate all the tracks.