At 8:45 AM -0400 10/15/98, Susan Duncan wrote:
>Thomas F. Maher, Jr. wrote:
>> Right now I have:
>>
>> Student Advisee
>> ----------- ---------------- Faculty
>> StudentID (1)- - - - - - (8) StudentID ------------------
>> [More] FacultyID (8) - - - - - - - - (1) FacultyID
>> [More]
>>
>
>Depending on how complex some of the relationships get, you may want to
>have one
>table for each group, and then a detail table that only contains the ID
>for each
>group. The detail table becomes the "glue" for whichever query you need
>to make.
>That is unless that is what you mean by the "Advisee" table (ie. Advisee
>is not a
>separate person).
susan this is what I thought he meant by the "advisee" table - it is
structured as the "glue" between student table and faculty table, using
only the IDs from the two.
And TJ -- when you get to the part where you NAME your tables -- if your
prof doesn't mention it -- you might want to differentiate between tables
w/data (student, faculty) and tables that indicate relationships (advisee).
in the naming convention we're using in the group i;m with, they would be
t_student
t_faculty
tr_advisee
kathy
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Kathy E. Gill, http://www.dotparagon.com/R65/
WWW design � writing � training - http://www.dotparagon.com/
Mac Advocacy - http://www.halcyon.com/kegill/mac/
Sometimes I wonder if men and women really suit each other. Perhaps they
should live next door and just visit now and then.
--- Katharine Hepburn
____________________________________________________________________
--------------------------------------------------------------------
Join The Web Consultants Association : Register on our web site Now
Web Consultants Web Site : http://just4u.com/webconsultants
If you lose the instructions All subscription/unsubscribing can be done
directly from our website for all our lists.
---------------------------------------------------------------------
