Posted by Summercoolness on 08/15/07 15:39

> You could start with atomic pieces of information and then look for
> relationships between them. For example, list Movies, Theaters, and
> ZipCodes on the board. Then it should be clear that there is a many-
> to-many relationship between Movies and Theaters, so you can add a
> relation for that. Then it should also be clear that there is a many-
> to-one relationship between ZipCodes and Theaters, so you can create a
> foreign key from Theaters to ZipCodes. It's not a substitute for real
> design work, but it might be enough for the 2-minute interview quiz.

will zipcode be just a property (a field) inside the theater table,
or will zipcode need to be a table itself?

• Next in forum: Re: standard and easy way to do schema design
• Prev in forum: Re: standard and easy way to do schema design
• Thread view: Re: standard and easy way to do schema design

[Reply to this message]