Um, that's why I said:

"and there certainly could be depending on the application - ie. What
school did you graduate from? vs. What school(s) have you attended"

And that's my point. For ONE school, a separate relational table is
unnecessary.

> grr!! it does fit in right.  it said GRADUATED FROM.  i've never known of
> anyone who has graduated from more than one high school :P
>
> ----- Original Message -----
> From: Tony Schreiber <[EMAIL PROTECTED]>
> To: CF-Talk <[EMAIL PROTECTED]>
> Sent: Wednesday, March 28, 2001 10:36 PM
> Subject: RE: database design question
> 
> 
> > I think your highschoolrelations table is overkill when there is only a
> > 1-1 relationship. If there were a small, finite number of schools, then
> > yes, a table of ids and names of those schools would be useful and you
> > would populate the highschool field of the user with that schools id. But
> > if there could be more than one school per user (and there certainly could
> > be depending on the application - ie. What school did you graduate from?
> > vs. What school(s) have you attended) then your relations table fits the
> > bill nicely.
> >
> > > Here is the question.  Diod they graduate from high school?  If so,
> which
> > > high school?
> > >
> > > Here is the inference.
> > >
> > > Those who have a high school name went to high school, and those who
> didn't
> > > have a high school name did not go to high school.  i know it's  a big
> DUH,
> > > but it's important.
> > >
> > > here's how i would dersign the database.  I would treat the high school
> name
> > > as a city, state or zip code, because there are thousands or gagillions
> of
> > > em.  So, i would put them in the same table as the client name
> > >
> > > so the client table would have another field called high school.  if
> it's
> > > null, then that means that they did not graduate from high school, and u
> can
> > > use that as a condition when u need that information.
> > >
> > > IF there were like only 10 high schools in the world, I would go about a
> > > different approach.
> > >
> > > I would have 3 tables.   1 table has the name of all the clients and
> their
> > > clientID (increment).  the 2nd table has the list of all high schools
> and
> > > their highschoolID (increment). The third table builds the relationship
> > > between the clients and their school.  the third table would have 3
> fields.
> > > The HighSchoolrelationsID, ClientID, and highschoolID.
> > >
> > > So if client Amy Gershen had a clientID of 3, and her high school James
> > > Brown High had a highschoolID of 12, this is the informationt hat would
> go
> > > into the Highschoolrelations table.
> > >
> > > HighschoolrelationsID     ClientID             HighSchoolID
> > > ---------------------     --------             ------------
> > >          1                   3                      12
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Julie Clegg [mailto:[EMAIL PROTECTED]]
> > > Sent: Wednesday, March 28, 2001 3:25 PM
> > > To: CF-Talk
> > > Subject: database design question
> > >
> > >
> > >
> > > hello,
> > >
> > > I am putting together a database and I cannot decide what to do with the
> > > Education Table.  I have 1000 clients who I need to enter their
> education
> > > level.  For example, did they graduate from highschool and if so, what
> is
> > > the name of their highschool.  Should I put that info on the same table
> or
> > > create a new table with the clientid and the name of the highchool
> attended
> > > if they did attend.  I know that if I put it all on one table there will
> be
> > > a lot of empty fields but I also didnt know if it was "wasteful" to
> create
> > > such a small table just for highschool name.
> > >
> > > What do you think?  Will the system slow down if I have ALOT of tables?
> > >
> > > Thanks,
> > >
> > > Julie
> > >
> > > >From: "Julia Green" <[EMAIL PROTECTED]>
> > > >Reply-To: [EMAIL PROTECTED]
> > > >To: CF-Talk <[EMAIL PROTECTED]>
> > > >Subject: Re: CF Books
> > > >Date: Tue, 20 Mar 2001 20:00:26 -0500
> > > >
> > > >Julie --
> > > >
> > > >This is late in coming, bu I have a great Adobe Acrobat Documentation
> book:
> > > >
> > > >http://www.allaire.com/documents/cf45docs/acrobatdocs/45dwa.pdf
> > > >
> > > >Julia Green
> > > >Julia Computer Consulting
> > > >PO Box 279
> > > >Watertown MA 02471-0279
> > > >http://www.juliagreen.com
> > > >Email:  [EMAIL PROTECTED]
> > > >Phone:  617-926-3413
> > > >FAX:  413-771-0306
> > > >
> > > >----- Original Message -----
> > > >From: Julie Clegg <[EMAIL PROTECTED]>
> > > >To: CF-Talk <[EMAIL PROTECTED]>
> > > >Sent: Monday, March 19, 2001 11:05 AM
> > > >Subject: CF Books
> > > >
> > > >
> > > > > Hello,
> > > > >
> > > > > Can anyone recommend a good CF developers book...we will be building
> a
> > > >new
> > > > > application using CF 4.5 and I need something that will be a good
> > > >reference
> > > > > book for a new CF developer!
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Julie
> > > > >
> > > >
> > >
> >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to