Re: Attribute-value approach for table design
- From: "Jeff Boyce" <JeffBoyce_IF@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 12 Nov 2006 05:24:28 -0800
Jamie
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.
Any additional evidence, or are we in the realm of opinion?
Thanks!
--
Regards
Jeff Boyce
Microsoft Office/Access MVP
http://mvp.support.microsoft.com/
Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/
Microsoft Registered Partner
https://partner.microsoft.com/
"Jamie Collins" <jamiecollins@xxxxxxxxxx> wrote in message
news:1162889532.808374.17220@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
column.
Ming wrote:
I am thinking to put the new fields into a new table, which will has
Attribute Name, TextValue, DateValue, NumberValue, and BooleanValue
I don't think you'll find much support for the notorious EAV
(Entity-Attribute-Value) 'design flaw' around here :(
Jamie.
--
.
- Follow-Ups:
- Re: Attribute-value approach for table design
- From: Jamie Collins
- Re: Attribute-value approach for table design
- References:
- Re: Attribute-value approach for table design
- From: Jamie Collins
- Re: Attribute-value approach for table design
- Prev by Date: Set up Due Date
- Next by Date: Re: Training records
- Previous by thread: Re: Attribute-value approach for table design
- Next by thread: Re: Attribute-value approach for table design
- Index(es):
Relevant Pages
|