Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make lando db-export use mariadb-dump, if it exists #148

Merged
merged 4 commits into from
May 2, 2024

Conversation

christopher-b
Copy link
Contributor

mysqldump is deprecated in current versions of MariaDB, and lando db-export generates a deprecation warning in these versions. This change allows db-export to use mariadb-dump if that command exists and the MARIADB_DATABASE env var is set.

Resolves lando/mariadb#47.

Instead of worrying about which versions of MariaDB use the new command, I'm checking if the command exists and using it if it does.

I have created a test for the MariaDB service.

`mysqldump` is deprecated in current versions of MariaDB, and generates a
deprecation warning. This change allows `db-export` to use `mariadb-dump`
if that command exists and the `MARIADB_DATABASE` env var is set.

Resolves lando/mariadb#47
Copy link

netlify bot commented Apr 17, 2024

Deploy Preview for lando-core failed. Why did it fail? →

Name Link
🔨 Latest commit 185a873
🔍 Latest deploy log https://app.netlify.com/sites/lando-core/deploys/6633ed9feb2bc000086a3d13

@reynoldsalec reynoldsalec merged commit 63f32f5 into lando:main May 2, 2024
17 of 25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

MariaDB 11 deprecates mysqldump, need an option to use else in lando db-export and lando db-import scripts
2 participants