Bug #34905 | Plugin variables of type enum don't receive their default value | ||
---|---|---|---|
Submitted: | 27 Feb 2008 21:14 | Modified: | 5 Sep 2008 6:26 |
Reporter: | Bill Mitchell | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.1.22 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[27 Feb 2008 21:14]
Bill Mitchell
[6 Mar 2008 17:39]
Bill Mitchell
Obviously there is a typo in the corrected fix, when I did the cut-and-paste. The suggested fix should read: if ((opt->flags & PLUGIN_VAR_TYPEMASK) != PLUGIN_VAR_SET) { if (opt->flags & PLUGIN_VAR_THDLOCAL) options->value= options->u_max_value= (uchar**) (global_system_variables.dynamic_variables_ptr + offset); else options->value= options->u_max_value= *(uchar***) (opt + 1); }
[27 Mar 2008 14:34]
Susanne Ebrecht
Please try with newer version: MySQL 5.1.23.
[14 Apr 2008 17:50]
Olivier Chédru
On Windows, with 5.1.23, I cannot get my plugin enum variable set from my option file whereas other options are. The default check_func_enum() is never called. Could both problems be related?
[27 Apr 2008 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[4 Aug 2008 4:47]
Valeriy Kravchuk
Please, try to repeat with a newer version, 5.1.26, and inform about the results.
[4 Aug 2008 8:57]
Olivier Chédru
It's OK with 5.1.26-rc: the enum plugin variable gets its default value as set by the macro MYSQL_SYSVAR_ENUM, and is also properly set from an option file.
[7 Aug 2008 9:00]
Susanne Ebrecht
So we can close this bug report?
[7 Aug 2008 9:08]
Olivier Chédru
Yes, thanks.
[4 Sep 2008 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[5 Sep 2008 6:26]
Valeriy Kravchuk
Closed as it seems fixed in 5.1.26.