This question is an exact duplicate of:
I am designing database for B2b market. Catalog: is Colletion of Product,size,prices,delivery date and other data.
I need to design catalog on basis of three datasourceType .On The basis of Datasource Type we will decide to share catalog fully ,Partially and inherted(Partially with extra attribute).
One customer can share catalog to other customer . Admin can create Catalog configuration where admin will select catalogname,datasource type for product,size,images,prices and these all configuration will be store in Catalogtable.
Data Source Type: Blank: First time Upload Catalog Data (Can Fully shared data i.e. product,size,image,price etc) Direct: It will reference Product data (It will reffer Other customer Catalog )
Inherited: It will reffer other customer catalog and select products and can add some more extra attributes
I need direction for Catalog sharing req.
My list of Tables where I am creating Master Table like CataLog,Product,Attribute,Attribute Group,AttributeType,datasourceType. There are other dynmaic tables for each catalog and associated products which we are createding physical sql tables with associated attributegroup.
CataLog,Product,Attribute,Attribute Group,AttributeType,datasourceType
Catalog_Dynamic_ Product_Dynamic_
These dynamic tables are associated with master tables using product code and catalog code.
In Case of Direct DataSourceType we don't need to create Product dynamic table as It refer product from previous Catalog product dynamic table
Is this Dynamic table creation for each catalog and associated product is good or I need to go for other approach.This approach will separate data in season wise catalog and associated product.But This approach will create lots of dynamic tables in 1 year for multiple seasons
second Is it possible to achieve the goal without dynamic table
Aucun commentaire:
Enregistrer un commentaire