Hi all.
I have a new project to tackle, and I would greatly appreciate your thoughts and input into how I'm tackling it. Here is an outline:
The project is a specific online catalogue for a technology reseller. Basically, they want to be able to catagorise their products. They want to have a number of categories for some products, but only one for others. For instance, to find a CISCO 1760 switch, you will have to drill down through NETWORKS --> SWITCHES --> CISCO --> 1000 SERIES --> 1760. But to find Microsoft Windows 2000 ME you will only need to drill down through SOFTWARE --> MICROSOFT --> WINDOWS ME.
The structure of the database as I see it is CategoryID(PK), CAtegoryName, Parent. Where Parent is the categoryID of the category 1 level obove itself. Parent is 0 if this category is at the root.
Has anyone tackled a project like this? Or do you have any thoughts that I haven't thought about?
G -GTM Solutions, Home of USITE-
-=
I have a new project to tackle, and I would greatly appreciate your thoughts and input into how I'm tackling it. Here is an outline:
The project is a specific online catalogue for a technology reseller. Basically, they want to be able to catagorise their products. They want to have a number of categories for some products, but only one for others. For instance, to find a CISCO 1760 switch, you will have to drill down through NETWORKS --> SWITCHES --> CISCO --> 1000 SERIES --> 1760. But to find Microsoft Windows 2000 ME you will only need to drill down through SOFTWARE --> MICROSOFT --> WINDOWS ME.
The structure of the database as I see it is CategoryID(PK), CAtegoryName, Parent. Where Parent is the categoryID of the category 1 level obove itself. Parent is 0 if this category is at the root.
Has anyone tackled a project like this? Or do you have any thoughts that I haven't thought about?
G -GTM Solutions, Home of USITE-
-=