You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In general, the mysql client shipped with the ddev-webserver works fine with all mariadb and mysql back-end databases.
However, there are a few cases where their behavior is slightly different.
And the fact that the mysql client reports a different version is often confusing to people.
For example, with database mysql:8.0 we see these outputs:
rfay@rfay-mbp-2021:~/workspace/d10$ ddev exec mysql --version
mysql Ver 15.1 Distrib 10.11.6-MariaDB, for debian-linux-gnu (aarch64) using EditLine wrapper
rfay@rfay-mbp-2021:~/workspace/d10$ ddev exec -s db mysql --version
mysql Ver 8.0.33-0ubuntu0.20.04.2 for Linux on aarch64 ((Ubuntu))
The web container has the mariadb version, and the db container has the mysql:8.0 version.
On Craft CMS and perhaps some other places, people have the habit of using the built-in tools; Craft actually calls out to the mysql client (on ddev-webserver) rather than connecting directly to the database server, so this can cause confusion there.
Add a layer to the ddev-webserver adding a matching mysql client to the ddev-webserver, especially where the database type is mysql:8.0, which is the most likely place for concern.
It also might be possible to implement this as an add-on for the few people it matters to. It's tricky getting the proper match between the OS-provided mysql client and the ddev-webserver, and it could introduce instabilities.
The text was updated successfully, but these errors were encountered:
rfay
changed the title
Install matching mysql client inside ddev-webserver based on mysql or mariadb database type
Install matching mysql/mysqldump client inside ddev-webserver based on mysql or mariadb database type
Apr 11, 2024
In general, the
mysql
client shipped with the ddev-webserver works fine with all mariadb and mysql back-end databases.However, there are a few cases where their behavior is slightly different.
And the fact that the
mysql
client reports a different version is often confusing to people.For example, with database mysql:8.0 we see these outputs:
The web container has the mariadb version, and the db container has the mysql:8.0 version.
On Craft CMS and perhaps some other places, people have the habit of using the built-in tools; Craft actually calls out to the mysql client (on ddev-webserver) rather than connecting directly to the database server, so this can cause confusion there.
Proposal
Add a layer to the ddev-webserver adding a matching
mysql
client to the ddev-webserver, especially where the database type is mysql:8.0, which is the most likely place for concern.It also might be possible to implement this as an add-on for the few people it matters to. It's tricky getting the proper match between the OS-provided
mysql
client and the ddev-webserver, and it could introduce instabilities.The text was updated successfully, but these errors were encountered: