i am a beginner and any response will help me a lot.
i have 20 types of products,
each product has about 40 fields, most of them are common fileds for all products, but some of them are unique.
the number of the unique fields of all the product types is 75.
the question:
Should i build one products table with 75 fields and leave nulls where a field is not property of a product type?
Or should i build a products table for the 30 common fields and a 20 different tables for each product type extra fields?
Or just build 20 different tables each product type?
other ideas are welcome
you can use Named-pair design technique that is very comon in Software as Service application where we have to maintained the list of customer and some customer can have attribtues that are uncomon to other.
create a table called ProductAttributs that can have column like
1- ProductAttributeID,Attribute Name , Data Type ,IsNull
then Create another table called Product Attribute Value that has column
1-ProductID
2-ProductAttribute ID
3- Value
and you have a base table Product which contains the common fields only
so by this first you can create a set of advance product attributes in Product Attribute Table
then bind your product table with Product Advance attributes in product attribute value so by this you can manage dynamic Product attributes that are not comon in ever Product.
|||
hi., please help me, i am a student, i have basic idea on webprogramming specially ASP.NET, actually im using Visual Web Developer.,
i have a new "complicated" project. i really need help.
1st. the data base, this is the diagram of the data, it is not the actual form but its more like this:
if i will do it in the form of access, it will look like this.
if you would look on the table and the diagram, there are just 2 lavel in the table which is in the diagram has 3 level.
thisis the story about that. the table also has 3 level, look on the Boldwords, if you would look on the many "angeles" there is also not so farbeneath a single "angles" but this time, he is under "balagtas", sothis is the levels, "Balagtas --> Angeles--> (bold names underangeles)" how to know the other names with same levels,
@. lookfor names that are inputed in many times in the "LinkFrom" header thenlook for the same name in the "LinkTo" header. so just look closely inthe table so you can under stand the format.
so this is the question, how can i design my database from access?? what will it look like?
after the database, this is the story for how should the web page operate.
@. assumption: that there will be 3 dropdown menu, each menu correspond to each level.
sofor example, if i choose an item in the level 3 dropdown menu, it willshow a table or info (if you would look in the table above, it will bethe numbers' "1's") for:
1. link from level 2 to level 3.
2. link from level 1 to level 2
so to make it short, will should detect he's original link were ever he was link to.
so if i select a value from the level 2 dropdown, it will only show the link from level 1 to level 2
if select a value from level 3 it will show link from level 2 to level 3 and level 1 tot level 2.
it should trace were he is connected so i think the real key here is the design of the database.
actuallythe table i show to you is the real table but i cut it to make itshort. so there are still some 3 level layer out there in the sameformation as the "Balagtas --> Angeles --> under angeles" intwo columns style.
i hope someone can help me tothis,...please. this day is friday here in the philippines, i willhave no class tomorow, only here in the school were i can work and openthis forum. i hope in monday there will be an answer. thanks in advanceto any person.
please feel free to ask it you want to know any clarification to my post.
SALAMAT PO...
