Help needed with designing database model

[warezguy05]

Hi

I'm developing a database driven website (my first one..) but i've run into a problem.

My vision:

The website should contain a database of DJ's that have played SETS at EVENTS (or raves ..whatever you call them). Each of those sets should contain a downloadlink to an audiofile so the visitors of the website are able to listen the set at home.
Every set consists out of a certain amount of TRACKS (id, artist, title, remixer)


Ok..till now it's easy, now the next part: I'd like to add a TRACKLIST to every set, so the visitors are able to see what tracks were played by the DJ during that specific set.

I thought about this solution:

In the 'track' entity i add the elements 'set_id' and 'position'.
The element 'set_id' will be the connection with the set the track has been played in. The element 'position' represents the position of the track within that tracklist. So if the position of a track is 8, it means that it is the 8th track that the dj played that night.
Now, when i join a few tables i should be able to show the visitors the tracklist of every set.

The problem is: When i apply this solution, i will have many duplicate tracks in my database. I want to integrate many sets and several dj's play the same records..

Is it a problem that i will have many duplicates in my database? If possible, the visitors should also be able to click on the track within a tracklist to see in what set it has been played. Is this possible to show the visitors such a track-page when having duplicates in a database or should i apply another solution?

Thanks for reading and i hope you guys understand my problem (and more important: can help me haha!!)

[chaarmann]

...
The problem is: When i apply this solution, i will have many duplicate tracks in my database. I want to integrate many sets and several dj's play the same records..

As is it shown in your graph, you are only referencing to a track through primary key.Each track has a primary key which should identify the track. So instead of inserting a "duplicate" track, you can just search for the one which is already there in the table and re-use its primary key.
In your other tables, you should insert many times this primary key. So you will have many references to only a single database record. This is different from having duplicate records.