| Bug #9886 | Mysql client hangs if delimiter is not used in an intermediate step | ||
|---|---|---|---|
| Submitted: | 14 Apr 2005 5:57 | Modified: | 28 May 2005 0:39 |
| Reporter: | Disha | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server | Severity: | S2 (Serious) |
| Version: | 5.0.3/5.0.5 BK | OS: | Windows (Windows 2003) |
| Assigned to: | Jim Winstead | CPU Architecture: | Any |
[14 Apr 2005 6:04]
MySQL Verification Team
c:\mysql\bin>mysql -uroot test
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1 to server version: 5.0.5-beta-nt
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql> delimiter //
mysql> Set @a=1;
-> Set @b=1
-> Set @c=1//
Query OK, 0 rows affected (0.03 sec)
Aborted
c:\mysql\bin>
[28 May 2005 0:39]
Jim Winstead
I wasn't able to repeat this on Linux/x86_64.

Description: Description: This bug might be similar to 9870. However, the repro steps we have are different and hence filing this. Moreover, in 9870, a delimiter is used and hence the hang. In this bug, the delimiter is not used, and therefore might be a different issue. The hanged client's status is 'Sleep', when we checked from another client. How to repeat: 1. delimiter // 2. Set @a=1; Set @b=1 Set @c=1// ACTUAL RESULT: Client hangs. EXPECTED RESULT: Syntax error. ERROR 1064 , should be displayed