nuclearsam Posted April 12, 2013 Share Posted April 12, 2013 Hi, When I was trying to export my products I found that the price field for combination is redundant in database. The price for a combination is stored in three different tables viz. `product_attribute`, `product_attribute_shop` and `attribute_impact`. On changing the combination price from BO the first two tables are updated, however on changing the price in first table directly from database doesnt reflect the updated price in BO. Can anyone tell me why they have stored price in three different table. As redundancy is the most stupid thing a DB architect can do. Thanks Sam Link to comment Share on other sites More sharing options...
NemoPS Posted April 12, 2013 Share Posted April 12, 2013 Yes, it's redundant, but only if you don't use multistore. If you do, product_attribute_shop becomes meaningful. Indeed, this should be the only one used from the beginning, but for some reason (retro-compatibility) the other 2 are used as well :/ Link to comment Share on other sites More sharing options...
nuclearsam Posted April 12, 2013 Author Share Posted April 12, 2013 this makes sense.. thanks however the third table `attribute_impact` is not updated on changing the impact on price from BO. I wonder how it will be helpful for retro-compatibility. Link to comment Share on other sites More sharing options...
Recommended Posts