| Bug #10516 | No error or warning message in getopt_ull_limit_value() | ||
|---|---|---|---|
| Submitted: | 10 May 2005 15:25 | Modified: | 8 Oct 2008 19:18 |
| Reporter: | Disha | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: Errors | Severity: | S3 (Non-critical) |
| Version: | 5.0.5-beta pre-release | OS: | Windows (Windows Server 2003) |
| Assigned to: | CPU Architecture: | Any | |
[10 May 2005 15:49]
MySQL Verification Team
Verified on Linux.
[24 May 2005 15:39]
Heikki Tuuri
Marko, please look at this, too, now that you are fixing 'very fast shutdown' which is designated by value 2. Regards, Heikki
[25 May 2005 11:01]
Marko Mäkelä
This is related to a bug I have reported previously: the methods in set_var.cc for setting options will silently cap the new option value to the limits. As you can see with SELECT @@global.innodb_fast_shutdown, the value was silently modified to 2. I guess my bug report has been reacted upon: trying to set the option negative will set it to zero rather than the positive maximum. I'm sorry that I couldn't find my original bug report.
[20 Jun 2007 9:34]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/29165 ChangeSet@1.2492, 2007-06-20 02:33:50-07:00, antony@ppcg5.local +2 -0 Bug#10516 "No error or warning message in getopt_ull_limit_value()" Validation does not emit any error messages if values are out of range. Perform checks when updating system variables when in STRICT mode. Initial commit for review.
[3 Aug 2007 16:12]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/32074 ChangeSet@1.2569, 2007-08-03 09:11:45-07:00, antony@pcg5ppc.xiphis.org +21 -0 Bug#10516 "getopt_ull_limit_value() does not show warnings or errors" Alter code so that when getopt_ull_limit_value() is used, there are checks performed to validate that the value is in range and to emit errors or warnings accordingly. New test: strict_variables
[3 Aug 2007 16:15]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/32075 ChangeSet@1.2569, 2007-08-03 09:14:49-07:00, antony@pcg5ppc.xiphis.org +20 -0 Bug#10516 "getopt_ull_limit_value() does not show warnings or errors" Alter code so that when getopt_ull_limit_value() is used, there are checks performed to validate that the value is in range and to emit errors or warnings accordingly. New test: strict_variables
[8 Oct 2008 19:18]
Konstantin Osipov
mysql> set @@global.innodb_fast_shutdown=5000000; Query OK, 0 rows affected, 1 warning (0.00 sec) mysql> show warnings; +---------+------+----------------------------------------------------+ | Level | Code | Message | +---------+------+----------------------------------------------------+ | Warning | 1292 | Truncated incorrect fast_shutdown value: '5000000' | +---------+------+----------------------------------------------------+
[8 Oct 2008 19:19]
Konstantin Osipov
Can't repeat against the latest 6.0 (6.0.8)
Description: If tried to set bigger value to system variable 'innodb_fast_shutdown' it accepts it. As it accepts the values 0 , 1 and 2 only then validation should be there. How to repeat: 1. delimiter // 2. create database test// 3. use test 4. set @@global.innodb_fast_shutdown=5000000// 5. Observe that the query is OK. No error or warning message is there. Expected Results: As it accepts values 0,1 and 2 only then for such a big value , error or warning message should be displayed. Actual Results : It accepts the big value. Validation of value is not checked.