Bug #6852 | prepared INSERT, updatable VIEW with check option, crash | ||
---|---|---|---|
Submitted: | 26 Nov 2004 19:51 | Modified: | 14 Jun 2005 19:12 |
Reporter: | Matthias Leich | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.0 | OS: | |
Assigned to: | Oleksandr Byelkin | CPU Architecture: | Any |
[26 Nov 2004 19:51]
Matthias Leich
[26 Nov 2004 19:53]
Matthias Leich
test case
Attachment: xnist1.test (application/test, text), 1.79 KiB.
[27 Nov 2004 23:10]
MySQL Verification Team
Thank you for the bug report I was able to repeat with latest BK source 5.0.
[29 Nov 2004 19:21]
Peter Gulutzan
I get a crash in similar circumstances (view with check option, OR in WHERE condition) without needing "prepare". Example: mysql> delimiter // mysql> create table ti2 (s1 char(2))// Query OK, 0 rows affected (0.31 sec) mysql> create view vi2 as select s1 from ti2 where s1 like '%' or s1 like '%' with check option// Query OK, 0 rows affected (0.01 sec) mysql> create procedure pi2 (param1 char(2)) begin insert into vi2 values (param1); end;// Query OK, 0 rows affected (0.00 sec) mysql> call pi2('a''5')// Query OK, 1 row affected, 1 warning (0.00 sec) mysql> call pi2('b`7')// ERROR 2013 (HY000): Lost connection to MySQL server during query
[10 Jan 2005 13:12]
Matthias Leich
I checked this bug with a fresh pulled and compiled MySQL 5.0 again. ChangeSet@1.1740, 2005-01-09 The bug disappeared.
[14 Jun 2005 19:12]
Oleksandr Byelkin
Yes it is not repeatable any more, thank you for bugreport!