This is a perfect example of where you should use a third table to connect composers and songs. This table known as a junction table would have one field for composerid and one for songid.
Always use separate fields for first and last names
Sent from mobile
I'm working on a database which can involve multiple composers. It's a
song database. My question is what is the best way to design the
composer name fields?
1. Use separate LAST NAME, FIRST NAME fields or just one name field?
2. Use separate COMPOSER NAME fields to allow those songs that have
multiple composers? Seems to say composer1, composer2, etc. would be
cumbersome because some will have more than three authors, etc.?
3. Of course, there will be a table of all composers.
Any ideas would be appreciated.
Jerry in Michigan, USA
Posted by: firstname.lastname@example.org
|Reply via web post||•||Reply to sender||•||Reply to group||•||Start a New Topic||•||Messages in this topic (2)|