Upgrading from MariaDB 10.3 to 10.6
Upgrading the MariaDB version from 10.3 to 10.6 brings some changes, but not every website is affected. If your websites and their plugins are kept up to date, you should not notice changes. In case you do experience problems with the functionality of your website, we have summarized some important changes for you in the following sections.
OFFSET
Self-written or very outdated applications with database access may be affected by this change.
The name OFFSET (case-insensitive) is a new reserved keyword under MariaDB 10.6. Make sure that all identifiers (e.g. database, table and column names) with this name are always correctly placed between so-called backticks (` `).
Example:
MariaDB [user_mydb]> SELECT `offset` FROM `mytable`;
+--------+
| offset |
+--------+
| 10 |
+--------+
1 row in set (0.000 sec)You can find more information on the official website of MariaDB:
- https://mariadb.com/kb/en/upgrading-from-mariadb-10-5-to-mariadb-10-6/#reserved-word
- https://mariadb.com/kb/en/reserved-words/
In such a case, we recommend contacting the developer of your application or the plugin directly, as the customization cannot be handled by Hostpoint on the server side.
UTF-8 charset
In MariaDB version 10.6 charset "utf8" was renamed to "utf8mb3" and the corresponding alias was added. The functionality itself has not changed. No adjustments are necessary on the server or in the databases. However, if an application explicitly requires "utf8" coding, this can lead to problems and impair the function of your website. These problems can generally be simply and permanently solved by replacing the name "utf8" with "utf8mb3". In that case, we recommend that you contact the manufacturer of your application or plugin directly, since Hostpoint cannot make the adjustments on the server side.
For more information, please consult the MariaDB official Website:
Outdated TYPO3 versions
The versions of TYPO3 affected by this change are outdated ones which have a strict character encoding requirement (CHARSET). However, only TYPO3 installations older than version 9.5 (LTS) are affected and they are no longer supported by the manufacturer. Please note that a paid support extension from the manufacturer is required in order to continue getting updates for version 9.5.
The incorrectly defined character encoding can be circumvented by manually adjusting the TYPO3 configuration in which the CHARSET is defined. To do this, you need to find the file LocalConfiguration.php in your TYPO3 installation, which is usually located in the folder typo3conf in the main directory of your website. In the file you should find the following block (or similar):
'DB' => [
'Connections' => [
'Default' => [
'charset' => 'utf8'
Adjust the configuration as follows from "utf8" to "utf8mb3" and save the file:
'DB' => [
'Connections' => [
'Default' => [
'charset' => 'utf8mb3'
If you can't find the above block in your configuration, this means you are using too old a version of TYPO3, one in which this workaround is not possible. In this case you will have to update your Website to a newer TYPO3 version.
For more information on the supported versions and their system requirements, you can visit the TYPO3 Website:
Magento
Magento has strict requirements as to which MariaDB versions are compatible with which Magento version. Notes on the versions and their requirements can be found here:
- https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/system-requirements.html
- https://experienceleague.adobe.com/docs/commerce-operations/release/versions.html?lang=en
As of version 2.4.6, which was released in March 2023, MariaDB 10.6 is also supported. You can circumvent the restriction to update or install version 2.4.5 or older under MariaDB 10.6 using the following procedures. With both options, an update as well as an installation should work again without any problems.
Option 1 - modify "di.xml"
One option to work around the problem is to customize the corresponding di.xml file where the version of MariaDB is defined. To do this, you need to find the di.xml file in your Magento installation. This is usually located in the root directory of your website. In the file you should find the following (or similar) structure:
<type name="Magento\Framework\DB\Adapter\SqlVersionProvider">
<arguments>
<argument name="supportedVersionPatterns" xsi:type="array">
<item name="MariaDB-(10.2-10.4)" xsi:type="string">^10\.[2-4]\.</item>
</argument>
</arguments>
</type>Now customize the structure as follows and save the file:
<type name="Magento\Framework\DB\Adapter\SqlVersionProvider">
<arguments>
<argument name="supportedVersionPatterns" xsi:type="array">
<item name="MariaDB-(10.2-10.6)" xsi:type="string">^10\.[2-6]\.</item>
</argument>
</arguments>
</type>
Option 2 - composer module
Another option is to use a corresponding composer module. This option has the advantage that the change remains even after an update.
You can find the module and more information here:
Further information
For more information on new features and official migration guides, visit the MariaDB website:
- https://mariadb.com/kb/en/changes-and-improvements-in-mariadb-10-4/
- https://mariadb.com/kb/en/changes-and-improvements-in-mariadb-10-5/
- https://mariadb.com/kb/en/changes-improvements-in-mariadb-106/
If you have technical problems with the upgrade, please contact our support team so that we can find a solution.
We are happy to help you with our experience.
Continuous updates save nerves
In general, it pays to always keep up with technology. If you update your CMS regularly and at short intervals, you have a clear advantage, and not just in terms of security. If you do not expect your CMS to make large version jumps (or overjumps), you also minimize the risk that comes with updates enormously. In most cases, the changes in updates from one version to the next (e.g. from 2.3 to 2.4 or from 1.8.2 to 1.8.3) are manageable, well tested and intended by the developers. Used themes and plugins usually survive such small update steps without damage.
The risk increases if you fall behind with the updates. In this case, many small harmless changes can gradually accumulate into incompatibilities or into dependencies - which can only be solved with a lot of effort. An unpleasant stress situation can then suddenly arise when you are forced to change the MariaDB version. That's why we recommend website operators to stay on the ball regularly with little effort and thus prevent the big update problems.
You can create a backup free of charge via the Hostpoint Control Panel and restore this in case of an emergency. Costs may be incurred for restores installed by customer support.
For support requests please use this form instead.
