Update linux tarball to mysql connector #3
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.
Hi @quinnj ,
Could the linux binaries pull the latest MySQL connector instead of mariadb v3.0.3?
The current linux mariadb binaries is causing an issue where we can't connect to MySQL 8.0. This is resolved in the latest mariadb connector (3.0.8), but this version no longer supports the
--enable-cleartext-pluginoption, which is required in certain PAM authentication set ups to connect to a MySQL server (mariadb to mariadb seems to work fine). Given this, the MySQL connector binaries seem like the best option - is there a reason that they're not currently used for linux and windows?I updated the
build_tarballs.jlfile to point to the MySQL connector linux files and did my best to make related updates in the script and products, but binary building is something I'm unfamiliar with. I also didn't touch the windows build file, but that probably should be updated to the MySQL connector as well.This should address MySQL.jl Issue 118.