Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Physical Database Design - Code Tables

Re: Physical Database Design - Code Tables

From: Dennis Williams <oracledba.williams_at_gmail.com>
Date: Tue, 21 Nov 2006 15:29:35 -0600
Message-ID: <de807caa0611211329p4f73b2e0s36b218144f20566@mail.gmail.com>


Paula,

One issue I don't see mentioned is the number of columns. In my experience, some codes tables have a different number of columns than others, and those columns may have different properties (data type, column name, etc.). If you use a single codes table, then all codes must have the same columns. If at a later point, some codes are found to need an additional column, then all codes will get the added column. If you add that column, then you have to hope that all the application code will be unaffected. This isn't probably a big deal, but I think it points to the non-normalized situation that a shared code table gets you into.

Dennis Williams

--
http://www.freelists.org/webpage/oracle-l
Received on Tue Nov 21 2006 - 15:29:35 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US