This would be a classic reason for using attributes.
If I correctly read your proposed structure for the products_sizes table as being a reference table, your needs are more directly reflective of pulling data from the Manufacturers table and simply storing the selected choice into your new "product_size" field in your products table:
- query the table
- build an array of its entries
- display a pulldown
- store the selected entry
- then in the storefront, display information appropriately based on the selected setting
- and build your shop-by-size choices in the category menu
That's yet another kettle of fish ... and doing it by using normal attributes would be admittedly more difficult. Using a dedicated size table as you're considering may be a touch easier. Nevertheless, I recall a contribution floating around some time back that had code for shop-by-size in it. It should be in the downloads section if you want to use it as a reference. I think it was attribute-based.
Bookmarks