Dima: thanks, I totally agree & appreciate your articulate validation.
Turkbear: here's a "normal" parts table:
id nbr name qty
1 10000001 widget 24
2 10000002 doohickey 189
and here's a row-driven parts table:
id attribute value
1 nbr 10000001
1 name...
A group at work claims that the familiar relational database table design of a row being an occurrence with attributes defined in each column does not work as well in applications as its reverse. For example, to add a column, location, to TableA which now has columns ID and Name means changing...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.