August 29th, 2004, 05:43 AM
|
|
Registered User
|
|
Join Date: Aug 2004
Posts: 22
Time spent in forums: 43 m 48 sec
Reputation Power: 0
|
|
|
database design question
i hope this isn't a daft question. i'm trying to create a database which is a catalogue of my dvds. so, some features of these dvds are things like subtitles, audio tracks, etc. so it seems fair that i have seperate tables for audio tracks and subtitles which the main dvd table references when necessary. but i'm confused about a method of referencing that reduces redundancy.
Say for example, that DVD #1 has only an english audio track and english subtitles. so for that record, i would have a field in the dvd table referencing the English records in both the audio tracks and subtitle tables.
But what if DVD #2 has english, french and japanese audio dubs? so i have a field in the dvd table for each audio track? AudioTrack1, AudioTrack2, AudioTrack3? That could potentially mean 20 different fields for audio tracks and for most records, most of them would be null and redundant.
The only other option i can think of, is that each DVD i own has several tables describing it, which seems just as redundant.
There must be a way to reference it without having a field every possible thing? And since it's common for DVDs to have, say, an English track, a French track, etc, surely it makes more sense to have a table that lists all the possible tracks and then reference from it as neccessary? It's really just a question of how to reference without the huge redundancy.
any help is appreciated!
|
Dev Articles Community Forums Sponsor:
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
