MDVA-43601: Triggers are removed from “catalogrule_product_price” table after full reindex

The MDVA-43601 patch fixes the issue where triggers are removed from catalogrule_product_price table after a full reindex of catalogrule_rule or catalogrule_product. This patch is available when the Quality Patches Tool (QPT) 1.1.13 is installed. The patch ID is MDVA-43601. Please note that the issue is scheduled to be fixed in Adobe Commerce 2.4.5.

Affected products and versions

The patch is created for Adobe Commerce version:

  • Adobe Commerce (all deployment methods) 2.4.2-p2

Compatible with Adobe Commerce versions:

  • Adobe Commerce (all deployment methods) 2.3.0 - 2.4.4
NOTE

The patch might become applicable to other versions with new Quality Patches Tool releases. To check if the patch is compatible with your Adobe Commerce version, update the magento/quality-patches package to the latest version and check the compatibility on the Quality Patches Tool: Search for patches page. Use the patch ID as a search keyword to locate the patch.

Issue

Triggers are removed from catalogrule_product_price table after a full reindex of catalogrule_rule or catalogrule_product.

Steps to reproduce:

  1. Set all the indexers to Update by Schedule.

  2. Check the triggers created for catalogrule_product_price table by running the following SQL request:

    show triggers like '%catalogrule_%'\G

  3. Manually reindex catalogrule_rule or catalogrule_product by running the following command: bin/magento indexer:reindex catalogrule_rule

  4. Check the triggers of catalogrule_product_price table again.

Expected results:

Triggers in catalogrule_product_price table are preserved after a full reindex.

Actual results:

No triggers are found for catalogrule_product_price table.

Apply the patch

To apply individual patches, use the following links depending on your deployment method:

To learn more about Quality Patches Tool, refer to:

For info about other patches available in QPT, refer to Patches available in QPT in our developer documentation.

On this page