MediaMonkey forum

I executed this sql command sequence in December 2025 and tried to execute it again today but it didn't work. If my query select didn't work either.

All this does is concatenate the date to the end of the title on tracks. Can you help me determine why this no longer works? I am still using MM version 2024.2.0.3163 because I am afraid to upgrade because everything is working so well in this version. Especially wifi synching!

this executed on 12-7-2025
UPDATE Songs
SET SongTitle = SongTitle || ' (' || substr(CAST(Year AS TEXT), 1, 4) || ')'
WHERE rowid IN (
SELECT rowid
FROM Songs
WHERE Year IS NOT NULL
AND length(CAST(Year AS TEXT)) >= 4
AND SongTitle NOT LIKE '% (' || substr(CAST(Year AS TEXT), 1, 4) || ')');

IE. The Beat Goes On Becomes The Beat Goes On (6701)

Well I just figured something out. I closed out of MM after executing my SQL Lite Concatenation commands and when I reopened MM, The command worked as all of my new titles had the correct date appended to the title. It just didn't show up right after the execution. Had to exit out of MM and then reopen it.

I don't get it but it is what it is.

We can close this out unless someone might have an explanation.

Have you tried any of the following:
1). Manual Rescan (Files > Add / Rescan)
2). F5 Refresh (current view)
3). DB / Tag Mismatch
4). Unsynchronised Tags Node

My feeling is you should also "UPDATE" the TrackModified field with something like: This will flag database records a "newer" than the "file" tags.

I feel it is good practise to close MediaMonkey before running any external SQL updates. This avoids lock contention and ensures that the application re-visits the library upon its next launch.

Actually, I would probably go for 1). Backup MM2024, 2). Close MM2024, 3). External SQL update. Then at least if something goes astray with the external SQL update, you can step back to the previous version.