|
BeTheBall -> RE: booking system (3/16/2004 11:45:04)
|
Technically, in a true relational database you would probably create a separate table just for categories. Makes it easier when you decide to add a category later. You would then use the category table as a lookup table in the DVD table. As far as what fields to use, that is up to you. All depends on how much information you want to store. In the category table, I would guess you will have just two fields. One will be something like, CategoryID and should be an autonumber and the primary key. The other will be simply Category. For the DVD table, the skies the limit. You will want to include the CategoryID field so that you can join the Category table, however, it will NOT be the primary key in the DVD table. You should have DVDID as an autonumber, primary key. DVD title and then anything else you can think of such as YearReleased, Rating, etc. Same goes for the Customer table. You will want CustomerID as an autonumber, primary key and then anything else you want. Does that help get you started?
|
|
|
|