Re: Attribute-value approach for table design

Jamie

I understand that some hold EAV in low regard ... I don't find the reasons
why (aside from potential performance). Can you point to some of the
reasons why you consider it a 'flaw'?

Regards

Jeff Boyce
Microsoft Office/Access MVP

"Jamie Collins" <jamiecollins@xxxxxxxxxx> wrote in message
news:1163406956.742760.309970@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Jeff Boyce wrote:
Can you offer some pointers to arguments both against and for EAV? A
cursory Google search suggested that there are performance issues in this
design, but that for something like a medical tests database, EAV offers
a
practical solution.

The intent of my post was to give a name to the design, using the word
'flaw' in quotes to reflect the low opinion in general application, to
encourage the OP to do some research. Mission accomplished ;-)

Let's face it: the chances of EAV being a newbie error, rather than
considered design choice, are extremely high.

Bear in mind that 'database' and 'SQL DBMS' are different concepts. My
impression from reading around the subject is that if EAV is the
required solution then SQL is not the best means to achieve those ends
i.e. 'performance issues' are a symptom of a fundamental bad fit.

My feeling is that the limited applications that benefit from EAV would
not be suited to an Access/Jet SQL.

Any additional evidence, or are we in the realm of opinion?

I've no first hand experience to add.

Jamie.

--



.

Relevant Pages