Bug #11478 | option new doesn't work as expected in 4.0 | ||
---|---|---|---|
Submitted: | 21 Jun 2005 11:02 | Modified: | 24 Jun 2005 12:32 |
Reporter: | Victoria Reznichenko | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 4.0 | OS: | Any (any) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[21 Jun 2005 11:02]
Victoria Reznichenko
[23 Jun 2005 11:36]
MySQL Verification Team
The second case is related to query cache. "SET new" doesn't flush relevant entries. mysql> select * from t2; +----------------+ | ts | +----------------+ | 20050623153446 | +----------------+ 1 row in set (0.00 sec) mysql> set new=1; Query OK, 0 rows affected (0.00 sec) mysql> select * from t2; +----------------+ | ts | +----------------+ | 20050623153446 | +----------------+ 1 row in set (0.00 sec) mysql> reset query cache; Query OK, 0 rows affected (0.00 sec) mysql> select * from t2; +---------------------+ | ts | +---------------------+ | 2005-06-23 15:34:46 | +---------------------+ 1 row in set (0.00 sec)
[24 Jun 2005 12:32]
MySQL Verification Team
Duplicate for #8894