| Bug #5519 | Stored procedure crash with GROUP_CONCAT_MAX_LEN = 0 | ||
|---|---|---|---|
| Submitted: | 10 Sep 2004 18:24 | Modified: | 10 Nov 2004 17:11 |
| Reporter: | Peter Gulutzan | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 5.0.2-alpha | OS: | Linux (SuSE 8.2) |
| Assigned to: | Per-Erik Martin | CPU Architecture: | Any |
[12 Sep 2004 20:56]
MySQL Verification Team
Verified against latest 5.0 BK source.
[10 Nov 2004 17:11]
Per-Erik Martin
This is not repeatable after the latest merge with 4.1. (show warnings shows the expexted warning)
Description: A stored procedure returns a "warning" if GROUP_CONCAT fails. Asking for SHOW WARNINGS after that causes a crash. I realize there is a workaround -- don't make GROUP_CONCAT fail by setting GROUP_CONCAT_MAX_LEN = 0 -- but it's a flaw. How to repeat: mysql> delimiter // mysql> set group_concat_max_len = 0// Query OK, 0 rows affected (0.00 sec) mysql> create table t (s1 char(5))// Query OK, 0 rows affected (0.27 sec) mysql> insert into t values ('abcde'),('fgh')// Query OK, 2 rows affected (0.00 sec) Records: 2 Duplicates: 0 Warnings: 0 mysql> create procedure p () select group_concat(s1) from t// Query OK, 0 rows affected (0.43 sec) mysql> call p()// +------------------+ | group_concat(s1) | +------------------+ | abcd | +------------------+ 1 row in set, 1 warning (0.00 sec) Query OK, 0 rows affected, 1 warning (0.00 sec) mysql> show warnings// ERROR 2013 (HY000): Lost connection to MySQL server d uring query