Bug #5515 SET GROUP_CONCAT_MAX_LEN doesn't flush query cache
Submitted: 10 Sep 2004 10:53 Modified: 10 Sep 2004 19:27
Reporter: Georg Richter Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1 + 5.0 OS:Linux (Linux)
Assigned to: Oleksandr Byelkin CPU Architecture:Any

[10 Sep 2004 10:53] Georg Richter 
Description:
Changing session variable GROUP_CONCAT_MAX_LEN has no effect, cause query cache will not be 
flushed. 

How to repeat:
5.0.2-alpha-debug-log 
[12:46] root@test> set session group_concat_max_len=10; 
Query OK, 0 rows affected (0.00 sec) 
 
5.0.2-alpha-debug-log 
[12:47] root@test> create table t1 (a varchar(20), b int); 
Query OK, 0 rows affected (0.05 sec) 
 
5.0.2-alpha-debug-log 
[12:47] root@test> insert into t1 values ('12345678901234567890', 1); 
Query OK, 1 row affected (0.00 sec) 
 
5.0.2-alpha-debug-log 
[12:48] root@test> select group_concat(a) FROM t1 group by b; 
+-----------------+ 
| group_concat(a) | 
+-----------------+ 
| 1234567890      | 
+-----------------+ 
1 row in set, 1 warning (0.00 sec) 
 
5.0.2-alpha-debug-log 
[12:48] root@test> set session group_concat_max_len=1024; 
Query OK, 0 rows affected (0.00 sec) 
 
5.0.2-alpha-debug-log 
[12:48] root@test> select group_concat(a) FROM t1 group by b; 
+-----------------+ 
| group_concat(a) | 
+-----------------+ 
| 1234567890      | 
+-----------------+ 
1 row in set, 1 warning (0.00 sec)
[10 Sep 2004 13:30] Oleksandr Byelkin 
ChangeSet 
  1.2019 04/09/10 16:28:18 bell@sanja.is.com.ua +5 -0 
  information about different variables agged to query cache (BUG#5515, BUG#5394)
[10 Sep 2004 19:27] Oleksandr Byelkin 
Thank you for bugreport. bug is fixed, patch is pushed in our source repository.