From: | Richard Broersma Jr <rabroersma(at)yahoo(dot)com> |
---|---|
To: | Nabil <Nabil(at)kramer-smilko(dot)com>, lefevre(dot)10(at)osu(dot)edu |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Mapping one to many |
Date: | 2007-06-13 18:05:42 |
Message-ID: | 402462.32723.qm@web31803.mail.mud.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
--- Nabil <Nabil(at)kramer-smilko(dot)com> wrote:
> Ahh but groups dont know about there members. It it was implemented
> the way that it has been suggested to me (a table for each users,
> groups and mapping user to groups) you would end up with a many to
> many relationship. The way I wanted to do it was just map user to
> groups without mapping groups to users. In other words map one user
> to many groups, the groups know nothing about the users.
What will you do when you have that you have to add more groups and delete other groups? Are you
going to redefine the dimementions of your array and the assignment of your array indexes as
records are added and deleted to your groups table?
A "many to many" table is really a relationship between two or more entity tables. The groups
table would know nothing about members and members would know nothing about groups. They way to
determine the relationship between members and groups is to query across the relationship table.
This is a time test any univerally accepted model for (Relational) database systems.
Regards,
Richard Broersma Jr.
From | Date | Subject | |
---|---|---|---|
Next Message | Ilan Volow | 2007-06-13 18:20:13 | Re: Mapping one to many |
Previous Message | Nabil | 2007-06-13 17:49:40 | Re: Mapping one to many |