I have a question about table design, it is not specifically related to MySQL.
The scenario is very simple: A person can own books, movies, songs etc.
Option 1 : Just one single table
person_name books songs movies
For this option, you can see, a lot of "NULL" have to be stored in the table
Attention: The post mess up the format, the book name should lineup with field
"books", sonngs should line up with field "songs", etc.
Option 2: Create as many table as necessary for books, songs, movies, etc.
As you see, in this option, no "NULL" need to be stored. However, you have a lot
of tables. Also, it will require union and other multi-table operations for some
search, which is not needed by the option1.