I'm designing a database schema for a music platform.
Some of the entities as follows:
A "track" can have an "artist". It can also have a "band" which makes the artist FK
Same goes with "album", an "album" can have an "artist" but if the "album" is from a "band" then the artist FK will be
null. That's because an "album" by a "band" can't also have a single "artist" as well.
The two(or three) FKs will never be filled together and only one of them must be filled for each record.
Is this a good design practice?