03-05-2024, 01:06 AM
Thanks, I did what you said and it appears to be working perfectly. I wish I had started out that way.
Regarding duplicate detection. It seems like if there were another column in the DB that had 'Songs.Path' separate from 'Songs.Title', then you could still do duplicate matching based on 'Songs.Title' independent of 'Songs.Path'. That would allow users like me to edit the path post-import. You could populate 'Songs.Path' with 'Songs.Title' (same functionality as now), or have an option that allows something like 'Artists.Name - Songs.Title' as the default.
You could add another option that defines how duplicate detection works: only on song name, or on song name and artist name.
Anyway, just food for thought from fellow programmer. I've been writing scripts to modify the DB for myself because I find that I need to do mass-edits sometimes and it's just faster to script them. A 'Songs.Path' column would solve a lot of problems for me.
Regarding duplicate detection. It seems like if there were another column in the DB that had 'Songs.Path' separate from 'Songs.Title', then you could still do duplicate matching based on 'Songs.Title' independent of 'Songs.Path'. That would allow users like me to edit the path post-import. You could populate 'Songs.Path' with 'Songs.Title' (same functionality as now), or have an option that allows something like 'Artists.Name - Songs.Title' as the default.
You could add another option that defines how duplicate detection works: only on song name, or on song name and artist name.
Anyway, just food for thought from fellow programmer. I've been writing scripts to modify the DB for myself because I find that I need to do mass-edits sometimes and it's just faster to script them. A 'Songs.Path' column would solve a lot of problems for me.