About Entity Relation Diagram

From: Silver <argytzak_at_med.auth.gr>
Date: Thu, 16 Dec 2004 14:09:16 +0300
Message-ID: <cprtnf$7dq$1@nic.grnet.gr>

Hi,

I 'm currently working on the ER diagram of a dating site.

I have this question about the tables that will contain the members data.

How can I organize the data so that the table remain as normalized as possible. In particular, I want my tables to be in the 3rd Normal form.

For example, the table with the member's APPEARANCE: will I have to have a table with the member's ID and then the columns: eyeColor, hairColor, Weight, BodyType, etc... ? That makes the table too large. Is there any other smarter way ?

What about the table with the member's PerfectPartner? Will I have to include the same attributes as in the APPEARANCE table? Again ?

The same problem occurs with the table INTERESTS. I want to have a list of predefined interests that the member can choose from, as well as a StringBox where one can enter something different. How can this be organized which as much as redundancy as possible??

I'm not asking to do this for me, just looking for advice on how to proceed.

Thanks!
Silver Received on Thu Dec 16 2004 - 05:09:16 CST