Re: EAV - again

On 2015-02-06, Erwin <e.smout_at_myonline.be> wrote:
> Op donderdag 5 februari 2015 22:50:44 UTC+1 schreef Eric:
>> We are used to hearing about EAV as a superficially clever idea which is
>> actually very bad. Not arguing with that at all. How might one look at
>> EAV?
>>
>> 1 as a way of providing end-user tailoring
>>
>> 2 as a way of adding entities and attributes without needing a database
>> Change Control
>>
>> 3 as a way of recording relationships between unstructured pieces of
>> data - http://geek-and-poke.com/?offset=1375995832310 (the data model
>> one) may be about this really
>>
>> So,
>>
>> * what is the right way to do 1?
>>
>> * how do you argue against 2 (and win)?
>>
>> * is 3 a legitimate need?
>>
>> Eric
>> --
>> ms fnd in a lbry
>
> What is your perceived difference between (1) and (2) ?.

1 is software designed around EAV as a way of providing end-user tailoring.

2 is developers trying to dodge the red tape they are supposed to work with

Eric

-- 
ms fnd in a lbry