None of this seems too terrible to handle. The title of the song can be an empty string, so use *string/Maybe string instead of string to distinguish between unset and "some idiot made the song literally untitled". I am surprised there are no songs that use characters only available in two different character sets, or are the same Chinese character repeated with multiple different writings (Simplified Chinese, Traditional Chinese, Korean, Japanese).

I suppose that some people are running into trouble by using CHARACTER VARYING(n) instead of TEXT in their database, but if you pick the most likely database for your local music player, then it doesn't matter. (sqlite doesn't care, basically.)

The song that's named after a virus test signature is amusing. I guess encrypt your filenames and database so that the OS can't pry into the details. Since you hopefully didn't write your music player in C, there should be no way that a virus can affect your music player.

(While I was researching this post, I found an interesting Defcon talk about what happens when you turn the EICAR virus signature into a QR code and scan it. https://www.youtube.com/watch?v=cIcbAMO6sxo A lot of stuff breaks! I almost got forced into adding similar breakage. At work we make what is essentially a database, and we got acquired by A Large Company, which had to do a security audit of our software. One of the "security vulnerabilities" in our product was that we don't scan the data in the database for viruses. We pushed back to not do this, because one of our customers literally uses our system to store viruses they analyze. But, it appears that a lot of other teams got this same suggestion and just made their price checker or passport validator crash when the barcode resolves to a virus. Easier than input validation or not calling `system(whatever the barcode resolved to)` I guess?)