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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The compatibility links MariaDB provides for MySQL commands are deprecated and will be removed in the future. We should use the MariaDB command name if that is the current MySQL provider.
The compatibility links MariaDB provides for MySQL commands are
deprecated and will be removed in the future. We should use the MariaDB
command name if that is the current MySQL provider.
Fixeswp-cli#271
@mrsdizzie How am I able to test your fix? I get the same issue on wp db import or wp db export after updating to PHP 8.4 and new bundles on the server.
@mrsdizzie How am I able to test your fix? I get the same issue on wp db import or wp db export after updating to PHP 8.4 and new bundles on the server.
This PR hasn't been merged yet so outside of checking out my personal branch here you'd need to wait until it gets reviewed and merged
I just updated to the latest db_command package and ran a wp db reset. I still get the same warning and the command fails. I think WP CLI doesn't get the correct system information. Check the screenshot below, especially the MySQL binary in the info section. The fix of this pull request is still running with mysql instead of mariadb in my case for that reason, I guess.
I don't think the PR actually touched wp db reset itself. It only changed mysqlcheck and mysqldump, as that's what the original report was about. It did not touch mysql. We use that in a few places still:
I don't think the PR actually touched wp db reset itself. It only changed mysqlcheck and mysqldump, as that's what the original report was about. It did not touch mysql. We use that in a few places still:
Yes, I'll think on the best way to do this since wp cli really does assume and use the mysql binary in many places. Probably an initial PR to wp-cli itself for a new utils function that returns the correct binary based on some heuristics (presumably people will have both installed at some point if they are intentionally separating to not be a drop in replacement anymore).
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The compatibility links MariaDB provides for MySQL commands are deprecated and will be removed in the future. We should use the MariaDB command name if that is the current MySQL provider.
Fixes #271
(We still use
mysql
all over the place in wp-cli, but that isn't going away from MariaDB.)