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: John Kanagaraj <john.kanagaraj_at_gmail.com>
Date: Tue, 21 Nov 2006 15:19:59 -0800
Message-ID: <2ead3a60611211519y6c212553l3a46bc148d300080@mail.gmail.com>


Paula,

This is a prime (and maybe extreme) example of a "one-size-fits-all" debacle as documented by our very own Tim Gorman http://www.simple-talk.com/opinion/opinion-pieces/bad-carma/ There are a few principles in the article that you should make the Developers read (the site itself is a SQL Server / .NOT oriented site :)

> I know that for developers having the generic, one-size-fits-all codetable
> is easier for them to code. However, I am very worried that having one
> generic codetable for all applications, all tables and all code fields could
> cause serious contention.
>
>

-- 
John Kanagaraj <><
DB Soft Inc
Phone: 408-970-7002 (W)

Disappointment is always inevitable; Discouragement is invariably optional

** The opinions and facts contained in this message are entirely mine and do
not reflect those of my employer or customers **

--
http://www.freelists.org/webpage/oracle-l
Received on Tue Nov 21 2006 - 17:19:59 CST

Original text of this message

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