Re: EAV - again
From: Eric <eric_at_deptj.eu>
Date: Thu, 5 Feb 2015 21:50:34 +0000
Message-ID: <slrnmd7pda.399.eric_at_bruno.deptj.eu>
Date: Thu, 5 Feb 2015 21:50:34 +0000
Message-ID: <slrnmd7pda.399.eric_at_bruno.deptj.eu>
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
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 lbryReceived on Thu Feb 05 2015 - 22:50:34 CET