Re: Mapping arbitrary number of attributes to DB
From: paul c <toledobythesea_at_dbms.yuc>
Date: Wed, 25 Oct 2006 01:57:44 GMT
Message-ID: <swz%g.187462$5R2.57713_at_pd7urf3no>
>> 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
>>
Date: Wed, 25 Oct 2006 01:57:44 GMT
Message-ID: <swz%g.187462$5R2.57713_at_pd7urf3no>
> 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 Received on Wed Oct 25 2006 - 03:57:44 CEST