diff options
author | unknown <anozdrin/alik@quad.opbmk> | 2008-03-28 18:10:04 +0300 |
---|---|---|
committer | unknown <anozdrin/alik@quad.opbmk> | 2008-03-28 18:10:04 +0300 |
commit | fba9e7c878359b0808e0f656d72aceedf34f0f56 (patch) | |
tree | dc8481ecdd397cf4753a4fb4ae0b826a319ed232 /.bzrignore | |
parent | 1abfb6e040c7c3b9b157d213cc4e46af3773ce20 (diff) | |
download | mariadb-git-fba9e7c878359b0808e0f656d72aceedf34f0f56.tar.gz |
A patch for Bug#34820: log_output can be set to illegal value.
We have "set" variables, which can accept empty values
(like sql_mode), and which can not (like log_output). The problem
was that the code does not distinguish them and allow empty
values for every set variable.
The fix is to introduce an attribute of a set variable telling
whether it can accept empty values.
mysql-test/r/variables.result:
Update result file.
mysql-test/t/variables.test:
A test case for Bug#34820: log_output can be set to illegal value.
sql/set_var.cc:
Don't allow empty values if it is prohibitted.
sql/set_var.h:
Add a flag (m_allow_empty_value) telling if an empty value is
acceptable for this variable.
Diffstat (limited to '.bzrignore')
0 files changed, 0 insertions, 0 deletions