Thanks guys. I thought that normalization would refer to redundant info not necessarily the same column names? I would further see the problem with the design if say phone_number in the agent table and lawyer table contained the same data, which of course they won't.
I thought about the "persons" table instead however you might notice that there are some columns that each do not have. Ie. home and work numbers for vendors and purchasers, firm for lawyers etc. Also I am expecting several columns to be NULL values for vendors and purchasers but not the other persons. I am very concerned with how I have setup the PK/FK/indices! Thanks guys! The repeated column names for example phone_number -----Original Message----- From: David T-G [mailto:[EMAIL PROTECTED] Sent: Friday, November 28, 2003 3:49 PM To: mysql users Cc: [EMAIL PROTECTED] Subject: Re: Please analyze my project table design -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! ...and then [EMAIL PROTECTED] said... % ... % I don't know of a DB theory rule that says it's a bad idea to have the same columns in many tables, but it might make the design more compact to take the common stuff and put it into one table. Oh, there is, indeed. CF "normalization" :-) HTH & HAND & good luck Paul :-D - -- David T-G * There is too much animal courage in (play) [EMAIL PROTECTED] * society and not sufficient moral courage. (work) [EMAIL PROTECTED] -- Mary Baker Eddy, "Science and Health" http://justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE/x8LcGb7uCXufRwARAq2vAKCDgl6tAoZyQMxRcuweK4fPFO8flQCfT1QU pJXdxLO02cnospbngiqMqzI= =eKBn -----END PGP SIGNATURE----- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
