Re: Mapping arbitrary number of attributes to DB

From: J M Davitt <jdavitt_at_aeneas.net>
Date: Thu, 26 Oct 2006 08:32:46 GMT
Message-ID: <Oo_%g.18807$pq4.14483_at_tornado.ohiordc.rr.com>


paul c wrote:

> J M Davitt wrote:
> 

>> Joshua J. Kugler wrote:
>>
>>> David Cressey wrote:
>>>
>>>> PMFJI.
>>>>
>>>> Now that I see what you are up against, I have a better handle on
>>>> why you
>>>> are perplexed.
>>>>
>>>> If I can generalize a little bit from what you've written here, you
>>>> want
>>>> a
>>>> data model that will be impervious to changing information
>>>> requirements.
>>>
>>>
>>>
>>> Actually, I just want a data model that can have a flexible number of
>>> attributes since various stations will have a flexible number of
>>> attributes. :)
>>>
>>> But I do understand the impossibility of preparing for every
>>> eventuality. I
>>> just want to be prepared for an eventuality I know will happen.
>>>
>>> j
>>>
>>
>> [I'm not recommending this, but...]
>>
>> I'm surprised that the entity-attribute-value design
>> hasn't been mentioned yet.
> 
> 
> I thought the majority here were trying to not mention it.
> 
> p

Let's get it out of the way and advise the OP that EAV is not a solution... Received on Thu Oct 26 2006 - 10:32:46 CEST

Original text of this message