serg, --base64-output=always, or just --base64-output - both has been planned for deprecation are buggy to produce unparsable output.
Andrei Elkin
added a comment - serg , --base64-output=always, or just --base64-output - both has been planned for deprecation are buggy to produce unparsable output.
Brandon Nesterenko
added a comment - - edited Hi Andrei,
I have implemented your suggested MTR test to compare --base64-output=auto against no specification.
The full patch is here
The buildbot link is here
Brandon Nesterenko
added a comment - Fix is implemented in 10.5.11 with no merge conflict observed when cherry-picking to 10.6.
10.6 Patch: https://github.com/MariaDB/server/commit/13e782eb84441d0c2ba1ce9d0109a7534d1995fa
Documentation updates for 10.6 to come.
MySQL 8.0 removed the 'always' option from --base64-output, and this fix follows that trend and removed the option from MariaDB. Additionally, now when --base64-output is specified, a value must be specified with it. When the flag is provided without a value, an error is presented.
Brandon Nesterenko
added a comment - MySQL 8.0 removed the 'always' option from --base64-output, and this fix follows that trend and removed the option from MariaDB. Additionally, now when --base64-output is specified, a value must be specified with it. When the flag is provided without a value, an error is presented.
People
Brandon Nesterenko
Xiyi Zhu
Votes:
0Vote for this issue
Watchers:
5Start watching this issue
Dates
Created:
Updated:
Resolved:
Git Integration
Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.
serg, --base64-output=always, or just --base64-output - both has been planned for deprecation are buggy to produce unparsable output.