Similar to the example given in the URL, cant we think of a subtype relation in this scenario? say Product (master table with the common attributes) and one table for each distinct category - camera/fridge/TV etc..
ProductID Name Manufacturer Type
1 P1 Canon Camera
2 P2 IFB Fridge
ProductID ISO Speed Zoom Resolution
1 --- ---- -----
if i want to sort the cameras by ISO speed, so i want to show the client the ISO speeds values to choose.
the question is if i want to sort also by resolution, or by any other attribute , should i have a table for each one and when i need to show that's values i will read from this table, what will bring to a situation that i have hundreds of tables
( ISO speed, resolution ,size...) or should i handle one huge table :