Forum Discussion

Satch's avatar
Satch
Icon for Helper III rankHelper III
9 years ago
Solved

Doubt about datamodel. How to approach

Hi,  have doubt about how to make datamodel.

It's because some tables have nested tables in it. I'll try to explain

 

Producttable 1:1 catalogtable

 

Now this catalogtable has f.e. 100 rows

But in this 100 rows are nested tables with each 4 filters (Color, size, material, trend)

So when I expand the filter.table column I get 100x4 catalog rows (4 per item, with each 4 different filters)

 

Would you suggest to expand as described above? I worry that some numerical values from catalogtable will be also x 4.

 

Or is it better to create separate table with catlog.id, filter.id

so it would be

                                                

Producttable 1:1 catalogtable 1:n  catalog, filter1

                                                       catalog, filter2

                                                       catalog, filter3

                                                       catalog, filter4

Need Help
  • TomMartens's avatar
    TomMartens
    9 years ago

    Hey,

     

    I would try to build a model loke this

     

    Product (one-side) - SKU (many-side), basically this could also be a single table with SKU as Unique-Identifier for a single row
    A SKU represents different variants of the same product, the SKUs differ by size, color, material, trend, these are just attributes from of SKU

     

    I would create a table catalog_sku that reflects the catalogID | SKU

     

    I would also create a catalog table and the following relationships

    SKU (one-side) - catalog_sku (many-side)

    catalog (one-side) - catalog_sku(many-side)

     

    Hope this gives you an idea

2 Replies

  • TomMartens's avatar
    TomMartens
    Icon for Super User rankSuper User
    9 years ago

    Hey,

     

    I would try to build a model loke this

     

    Product (one-side) - SKU (many-side), basically this could also be a single table with SKU as Unique-Identifier for a single row
    A SKU represents different variants of the same product, the SKUs differ by size, color, material, trend, these are just attributes from of SKU

     

    I would create a table catalog_sku that reflects the catalogID | SKU

     

    I would also create a catalog table and the following relationships

    SKU (one-side) - catalog_sku (many-side)

    catalog (one-side) - catalog_sku(many-side)

     

    Hope this gives you an idea

  • mperez080482's avatar
    mperez080482
    New Member
    8 years ago

    Is possible that if I do a word document in a 2003-2007 format, when I´ll try to open it in a 2010 or other format, change its properties, for example: arbitrary spaces between words are generated, source changes and size of this, etc; arbitrary inter lines spaces, etc.