Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>What you want to do might be possible, but I am not sure that the approach you have described would be doable, I think it is too simplistic to work with the very complex Magento platform. </p> <p>I had a similar project where the actual price of the products was constantly changing based on a few inputs and I was able to solve the problem fairly well, but it was definitely more complicated thank what you seem to be hoping for. I am not sure this scenario is helpful to you or not, but here it goes...</p> <p>The basic idea was that I created new product attributes (eav attributes). These served as the inputs to determine what the price really should be. Note that in my case, these attributes were being updated fairly regularly by an outside process.</p> <p>Then I created an observer on the "catalog_product_save_before" event that would simply do something like this:</p> <pre><code>//some calculations to get the $newPrice $product-&gt;setPrice($newPrice); </code></pre> <p>So basically that will make it so that the price field will always be current whenever you save a product in the administrative screens.</p> <p>Then also, since several of the attributes that were used as inputs were constantly changing (updated by an outside process), so we also had to add a magento cron job to run every so often, and it would recalculate the price for all the affected products with something like this...</p> <pre><code>//some calculations to get the $newPrice $product-&gt;addAttributeUpdate("price", $newPrice, Mage::app()-&gt;getStore()-&gt;getStoreId()); </code></pre> <p>So it all boils down to the fact that you should have the attribute saved in the db. And of course you need to find the specific spots of where to update that derived attribute. Maybe your requirements will vary slightly from what I have described, but it might get you on the right path at least.</p>
    singulars
    1. This table or related slice is empty.
    1. POMagento - Calculated Product Attribute (property)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USshaune
    1. USshaune
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMagento - Calculated Product Attribute (property)
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks a lot for your suggestion. I'm trying to eliminate the need of using observers and a cron job to update the field. If the Calculated Attributes idea is not possible, then your suggestion would a good work around. Let's see if somebody knows if and how Calculated Attributes could be achieved.
      singulars
      1. PO
      1. USmas
    2. COThe real challenge is getting the layered navigation and sortable listings to work without a field in the db. It probably can be done, but I imagine it will be a mucketty solution. Best of luck.
      singulars
      1. PO
      1. USshaune
    3. COYes, you're right - layered navigation and list sorting seem to require DB fields due to the paging.
      singulars
      1. PO
      1. USmas
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload