We occasionally come across cases where well-intentioned schema constraints block genuine data from being entered into a long-standing database. But it usually happens in huge business-oriented databases run by big companies. Two common examples are the bank customer with the surname 'To', and anything involving the town named Scunthorpe in England.

However, a common toy teaching example is an Artist/Album/Single database which is seen as too simple to have such problems. I enjoyed this article

https://dustri.org/b/horrible-edge-cases-to-consider-when-dealing-with-music.html

which gives numerous examples of how small-scale non-bureaucratic real-world data can make life difficult for someone who likes CHECK and UNIQUE keywords.

It ends with a link to the documentation for the MusicBrainz database schema, which, of course, has to cope with all this silliness.

You could try playing that unknown song to Shazam, and services like that. It has a web-facing interface. You don't need to download or install anything.

Frankly, I think any artist who doesn't give their work a name which can be easily typed is just giving up any money they could make from it. But that's just me.