J
John G
I want to design a database for a business that
manufactures UPVC windows and doors. My initial problem
is that each product (especially the windows)can be made
in various set sizes with set prices dependent on height
and width.
I know creating a separate table for each product is
ridiculous, epecially when products will also most
certainly be added or removed and the prices may change
over any period of time.
A more reasonable solution is to create one table with
each product's height and width matched with it's price,
but this also seems a bit much when lets say you there's
100 products with 100 different set sizes and costs.
I can accept that my thinking is probaly niave as I'm
fairly new to database design, so any ideas on how to
approach the problem would be appriciated.
thanks John
manufactures UPVC windows and doors. My initial problem
is that each product (especially the windows)can be made
in various set sizes with set prices dependent on height
and width.
I know creating a separate table for each product is
ridiculous, epecially when products will also most
certainly be added or removed and the prices may change
over any period of time.
A more reasonable solution is to create one table with
each product's height and width matched with it's price,
but this also seems a bit much when lets say you there's
100 products with 100 different set sizes and costs.
I can accept that my thinking is probaly niave as I'm
fairly new to database design, so any ideas on how to
approach the problem would be appriciated.
thanks John