Re: Large databases

Hello,

So it is true that tables can be (or should be less than 4 columns). This makes the database an academe's dream since all academics care about is theoretically correct database design.

BUT, don't you think it is very hard to maintain? Having about 10 tables instead of one. I have been involved in software development for a while and I do know that the KISS rule applies. If you make things too properly designed, then it will be too hard to keep it proper and a lot of bugs will show up since the system becomes too complicated to be understood by the common joe developer.

I better tell that Access DBA he was right after all.

--
Lyndon Tiu




> ----- Original Message -----

> To: "Multiple recipients of list ORACLE-L" <ORACLE-L_at_fatcity.com>

> Sent: 16 April 2003 21:43

>

> > CREATE TABLE PERSON (

> >    PERSON_ID NUMBER,

> >    FNAME VARCHAR2(20),

> >    MNAME VARCHAR2(20),

> >    LNAME VARCHAR2(30),

>

>         Denormalize names - First/Middle/Last is not the only option:

>                 (person_id, name_position, name)

>

> >    RACE_ID NUMBER(25), /*allows for proliferation

> > of pc categories */

>

>         Denomralize:

>             (person_id, race_id, percentage)

>

> >    BIRTH_DATE DATE,

> >    AGE NUMBER(3),

>

>            Derived information - eliminate

>

> >    HANDEDNESS CHAR(1),

> >    SEX CHAR(1),

>

>         Denormalize:

>             (person_id, date_form, sex)

>

> >    HEIGHT NUMBER(3),

>

>         Denomralize

>             (person_id, date_measured, height)

>

> >    WEIGHT NUMBER(3),

>

>             as above

>

> >    WAIST NUMBER(2),

>

>             as above

>

> >    INSEAM NUMBER(2),

>

>             (person_id, left_right, date_measured, length)

>

> >    COLLAR NUMBER(2),

>

>             as waist

>

> >    ARM_LEN VARCHAR2(5),

>

>             as inseam

>

> >    HAT_SIZE VARCHAR2(4),

>

>             as waist

>

> >    SHOE_SIZE VARCHAR2(5),

>

>             as inseam

>

> >    EYE_COLOR_CD VARCHAR2(3),

>

>             (person_id, left_right, colour_code)

>

> >    HAIR_COLOR_CD VARCHAR2(3),

>

>             (person_id, date_measured, colour_code)

>

> >    MARRIED CHAR(1),

>

>             (person_id, date_from, status)

>

> >    EDUCATION_CD NUMBER(1),

>

>             (person_id, date_achieved, code)

>

> > )

>

> which brings us down to:

>     person_id

>     birth_date

>     handedness  -- (but what if you lost your arm, and learned ?!)

>

> Um !

>

> > Now, that's over 20 and afaik normalized, no repeating groups, no

> > dependency on non key atttibutes, just to point out that aribitrary

> > numerical limits don't mean much if no business requirements are in

> > view.

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Lyndon Tiu
  INET: ltiu_at_alumni.sfu.ca

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).