by --CELKO-- <jcelko212@[EMAIL PROTECTED]
>
Jun 19, 2008 at 10:31 AM
>> I suggest that instead we create a more generic table that stores
various codes used within a schema, along with corresponding description
and a code 'category'. Another table (optional but recommended) would
contain 'category' descriptions. <<
The name of this design fallacy is OTLT ("One True Lookup Table") or
MUCK ("Massively Unified Code Keys"). You can Google around more
details or read Section 4.4 of THINKING IN SETS: AUXILIARY, TEM****AL
AND VIRTUAL TABLES.
>> This is not my idea, I've seen this approach used at other companies.
<<
Me, too. I charge them $1K-2K per day to clean up stuff like this.
