Magento 2.4.7 MySQL 8.4 support

[iwanzijderveld]

Description

Following the current platform requirements Magento 2.4.7 does not work with MySQL 8.4 LTS. Since MySQL 8.0 will be EOL in 6 months can we expect the next patch for 2.4.7 support MySQL 8.4? Or will it only work with a deprecated product?

Expected behavior

Support for MySQL 8.4

Benefits

Work with up to date software.

Additional information

No response

Release note

No response

[m2-assistant]

Hi @iwanzijderveld. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[engcom-Bravo]

Hi @iwanzijderveld,

Thanks for your reporting and collaboration.

Considering this as a Enhancement and marking this as a Feature Request.

Thanks.

[renttek]

@iwanzijderveld I have one 2.4.6 store running on MySQL 8.4 and haven't had any problems so far 🙂
We had to patch 3 files using composer patches for this.

1. in magento/framework:

--- DB/Adapter/SqlVersionProvider.php	2025-08-04 21:35:56
+++ DB/Adapter/SqlVersionProvider.php	2025-10-13 15:11:40
@@ -39,6 +39,8 @@

     public const MARIA_DB_10_11_11_VERSION = '10.11.11';

+    public const MYSQL_8_4_VERSION = '8.4.';
+
     /**#@-*/

     /**

2. In magento/magento2-base:

--- app/etc/di.xml	2025-08-04 21:41:18
+++ app/etc/di.xml	2025-10-13 15:10:35
@@ -1853,6 +1853,7 @@
         <arguments>
             <argument name="supportedVersionPatterns" xsi:type="array">
                 <item name="MySQL-8" xsi:type="string">^8\.0\.</item>
+                <item name="MySQL-8.4" xsi:type="string">^8\.4\.</item>
                 <item name="MySQL-5.7" xsi:type="string">^5\.7\.</item>
                 <item name="MariaDB-(10.2-10.11)" xsi:type="string">^10\.([2-9]|10|11)\.</item>
             </argument>

3. In magento/module-catalog:

--- etc/db_schema.xml	2025-06-02 22:48:36
+++ etc/db_schema.xml	2025-10-13 15:13:01
@@ -31,6 +31,9 @@
         <index referenceId="CATALOG_PRODUCT_ENTITY_SKU" indexType="btree">
             <column name="sku"/>
         </index>
+        <constraint xsi:type="unique" referenceId="CATALOG_PRODUCT_ENTITY_ENTITY_ID">
+            <column name="entity_id"/>
+        </constraint>
     </table>
     <table name="catalog_product_entity_datetime" resource="default" engine="innodb"
            comment="Catalog Product Datetime Attribute Backend Table">

Obviously, this is to be used at your own risk, but it was a good workaround for my situation (server had to be updated & had to get MySQL 8.4) until we bring the 2.4.8 update live soon 🙂