[Sahana_proj] wait a second...

[Antonio Alcorn]

Kumud- you're right.
This example could indeed be accomplished with one table, but the
intent is to give some experience with the relational database model.
This is a way of storing information such that it maintains
information about relationships between different pieces of data, and
prevents unnecessary data duplication, among other things. Here's a
pretty good quick intro:
http://www.databasejournal.com/sqletc/article.php/1469521
(see the poets/poems example under "The Relational Database  Model").

As systems become large and complicated this becomes really useful.

Antonio

On 2/19/07, Kumud Nepal <kumud.nepal at trincoll.edu> wrote:
> i think the problem is to link up one attribute from one table to
> another and then print them out.. .correct me if i am wrong...
>
> Bobby DeSimone wrote:
> > is there any particular reason we need three tables to do this?
> > Something is lost on me.
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Sahana_proj mailing list
> > Sahana_proj at lists.trincoll.edu
> > http://lists.trincoll.edu/cgi-bin/mailman/listinfo/sahana_proj
> >
>
> --
> Kumud Nepal
> 860-478-2161
> Trinity College
> Class of 2009
> 300 Summit Street
> Hartford, CT-06106
>
>
>
>
> _______________________________________________
> Sahana_proj mailing list
> Sahana_proj at lists.trincoll.edu
> http://lists.trincoll.edu/cgi-bin/mailman/listinfo/sahana_proj
>