reessolutions / db-override
reessolutions/db-override
A module to enable experimental MariaDB 10.5-11.x support before official support is available.
ReesSolutions DBOverride
Override Module to allow MariaDB 10.5 to 11.x support for development.
Now available via https://packagist.org/
Use this module at your own risk in production. Versions higher than MariaDB 10.4 have no official support.
Version Compatibility Matrix
| MariaDB Version | Support Status |
|---|---|
| 10.2 - 10.11 | ✅ Supported |
| 11.x | ✅ Supported (Experimental) |
| 11.4.8 | ✅ Tested |
Installation
- Require the Module
composer require reessolutions/db-override
Configuration
The module automatically supports the following database versions:
- MySQL 5.7.x
- MySQL 8.0.x
- MariaDB 10.2-10.11
- MariaDB 11.x (including 11.4.8)
Usage
After installation, the module will automatically allow Magento to connect to unsupported MariaDB versions.
No additional configuration is required.
Troubleshooting
If you encounter issues with MariaDB 11.4.8:
- Ensure you're using the latest version of this module
- Clear Magento cache:
bin/magento cache:flush - Check Magento logs for specific error messages
- Verify your MariaDB installation is functioning correctly
Migration Notes
When upgrading from MariaDB 10.x to 11.x:
- Backup your database before upgrading
- Test in a development environment first
- Review MariaDB 11.x release notes for breaking changes
- Update your database configuration if needed
Support
This module is provided as-is for development purposes. For production environments,
it's recommended to use officially supported database versions.
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 1.1.3 | stable | Pass | Magento 2.4.7-2.4.9 Details | 2026-06-18 19:16:16 |
| 1.1.2 | stable | Pass | Magento 2.4.7 Details | 2026-04-13 14:34:05 |
| 1.1.1 | stable | Not tested | Not yet tested Details | 2026-04-13 14:28:07 |
| 1.1.0 | stable | Not tested | Not yet tested Details | 2025-11-19 06:51:34 |
| 1.0.7 | stable | Not tested | Not yet tested Details | 2024-09-02 12:55:51 |
| 1.0.6 | stable | Not tested | Not yet tested Details | 2023-09-13 06:21:16 |
| 1.0.5 | stable | Not tested | Not yet tested Details | 2023-09-12 11:03:10 |
| 1.0.4 | stable | Not tested | Not yet tested Details | 2023-02-20 10:54:48 |
| 1.0.3 | stable | Not tested | Not yet tested Details | 2023-02-19 08:53:23 |
| 1.0.2 | stable | Not tested | Not yet tested Details | 2022-05-21 02:02:12 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2022-03-28 18:02:44 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2021-12-28 16:23:39 |
Requires 1
| Package | Constraint |
|---|---|
| php | ~7.2.0 || ~7.3.0 || ~7.4.0 || ~8.1.0 || ~8.2.0 || ~8.3.0 || ~8.4.0 || ~8.5.0 |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge — a phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases. Cell → details modal.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
Turn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.