% 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 :-)
Well of course, but that begs the question,
Greetings, my hands on school project is a small real estate database.
I am using MySQL 3.23 without InnoDB, but would like to migrate to 4.x
w/InnoDB at some point.
I would greatly appreciate any feedback on this design.
These are the business rules:
1) 1 matter may have several vendors
From: Paul Fine [EMAIL PROTECTED]
Date: 2003/11/28 Fri AM 11:14:25 CST
To: [EMAIL PROTECTED]
Subject: Please analyze my project table design
Greetings, my hands on school project is a small real estate database.
I am using MySQL 3.23 without InnoDB, but would like to migrate to 4.x
w
-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.
From: David T-G [EMAIL PROTECTED]
Date: 2003/11/28 Fri PM 03:49:17 CST
To: mysql users [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: Re: Please analyze my project table design
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
...and then [EMAIL PROTECTED] said...
%
...
% I
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
% 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 :-)
Well of course, but that begs the question, which
Paul,
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.
The layout would
From: Stefan Hinz [EMAIL PROTECTED]
Date: 2003/11/28 Fri PM 04:45:24 CST
To: [EMAIL PROTECTED]
CC: David T-G [EMAIL PROTECTED], mysql users [EMAIL PROTECTED]
Subject: Re[3]: Please analyze my project table design
% I don't know of a DB theory rule that says it's a bad idea to have
From: Paul F [EMAIL PROTECTED]
Date: 2003/11/28 Fri PM 04:35:04 CST
To: 'mysql users' [EMAIL PROTECTED]
Subject: RE: Please analyze my project table design
Thanks guys. I thought that normalization would refer to redundant info not
necessarily the same column names? I would further
10 matches
Mail list logo
