Database design - alternatives for Entity Attribute Value (EAV)

Posted by Bob on Stack Overflow See other posts from Stack Overflow or by Bob
Published on 2010-05-24T08:44:22Z Indexed on 2010/05/24 10:11 UTC
Read the original article Hit count: 463

Filed under:


see for similar topic.

My question: i want to design a database, that will be used for a production facility of different types of products where each product has its own (number of) parameters. because i want the serial numbers to be in one tabel for overview purposes i have a problem with these different paraeters .

One solution could be EAV, but it has its downsides, certainly because we have +- 5 products with every product +- 20.000 serial numbers (records). it looks a bit overkill to me...

I just don't know how one could design a database so that you have an attribute in a mastertable that says: 'hey, you could find details of this record in THAT detail-table". 'in a way that you qould easely query the results)

currenty i am using Visual Basic & Acces 2007. but i'm going to Visual Basic & MySQL.

thanks for your help.


© Stack Overflow or respective owner

Related posts about sql

Related posts about database