Re: standard and easy way to do schema design
Date: Wed, 15 Aug 2007 08:32:45 -0700
On 15 Aug, 16:29, "David Cressey" <cresse..._at_verizon.net> wrote:
> "Captain Paralytic" <paul_laut..._at_yahoo.com> wrote in message
> > On 15 Aug, 16:12, Doug_McMa..._at_yahoo.com wrote:
> > > On Aug 15, 4:08 am, Summercooln..._at_gmail.com wrote:
> > > > I wonder instead of just brainstorming, there probably is
> > > > a very standard and a simple way to do database schema design.
> > > > let's say we are doing a website. the user can go over
> > > > and type in the movie name and zipcode, and the website
> > > > will return all the theaters showing that movie and at what
> > > > time, for theaters in THAT zipcode only (for simplicity).
> > > > so how do we just start and use a standard method that
> > > > can be simple and very accurate to ensure good tables design?
> > > 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.
> > Wouldn't it be one-to-many between ZipCodes and Theatres or do you
> > really have theatres that big?
> I know of a theater in northern Vermont/southern Quebec that straddles the
> international border.
> An unusual case, though. Not worth altering the model.- Hide quoted text -
> - Show quoted text -
I wondor, if the 2 countries have different views on censorship, can certain parts of a scene only be played on one part of the stage? Received on Wed Aug 15 2007 - 17:32:45 CEST