Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
packymyles
Starting Member
21 Posts |
 Posted - 2008-08-05 : 11:02:16
|
| a song ID represents one SONG, but each Song has a few reccommended songs, which are represented by their Song ID and their Song name. So a Song has its own songid and song name listed, but also has a section for recommendations that lists a few other songsIDs and songNames. how would I make tables for these? songIDs and Songnames are unique but it's easier to use ID's as primary key. I was confused with how to make separate relationships that call from the same thing basically...Thanks |
|
|
packymyles
Starting Member
21 Posts |
Posted - 2008-08-05 : 13:49:52
|
| is there any way to do this without having a different name for song names and id's under recoommendations compared with song's ids and names in it's main song page? |
 |
|
|
packymyles
Starting Member
21 Posts |
Posted - 2008-08-05 : 13:55:26
|
| what im trying to picture is table: song-----------PK: song idsongnametable: Recommendations--------------- songIDsongnameI would want songid and songname in both tables to the calling info from the same places so it's not redundant, but I don't think this is the right table set up for such a thing? And recommendations are basically "songid"s that are referred from another "songid"THanks |
|
|
|
LoztInSpace
Aged Yak Warrior
940 Posts |
Posted - 2008-08-06 : 10:19:19
|
| I think you just need a table with 2 songIDs - one for the song & one for the recommendation. |
|
|
|
|
|
|
how should i make this relationship with tables