Re: Mapping arbitrary number of attributes to DB
From: J M Davitt <jdavitt_at_aeneas.net>
Date: Tue, 24 Oct 2006 23:44:04 GMT
Message-ID: <8zx%g.17928$OE1.3219_at_tornado.ohiordc.rr.com>
>
>
> 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: Tue, 24 Oct 2006 23:44:04 GMT
Message-ID: <8zx%g.17928$OE1.3219_at_tornado.ohiordc.rr.com>
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. Received on Wed Oct 25 2006 - 01:44:04 CEST