>>> On 6/19/2008 at 2:57 AM, in message
<Cbp6k.4005$Qu5.1469@[EMAIL PROTECTED]
>, Marco
Mariani<marco@[EMAIL PROTECTED]
> wrote:
> Frank Swarbrick wrote:
>
>> This is not my idea, I've seen this approach used at other companies.
>> Please see attached for an illustration.
>> Let me know what you think."
>>
>> I'd like to know how other companies do this. Do you have a separate
> table
>> for each set of codes or do you have one table with basically three
> columns:
>> code_category, code_value, code_description (or just catagory, value,
>> description)?
>
> The "one big Entity-Attribute-Value table" is a well-known DB
> anti-pattern, i.e. a common mistake.
>
> It _might_ make sense sometimes, but most of the times it doesn't.
That was my thought. I will try to discourage them from this path.
Thanks!
Frank
|
