Bug #31866 MySQL Server crashes on SHOW CREATE TRIGGER statement
| Submitted: | 26 Oct 2007 0:36 | Modified: | 19 Nov 2007 5:10 |
|---|---|---|---|
| Reporter: | Mikhail Serov | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Stored Routines | Severity: | S1 (Critical) |
| Version: | 5.1.22-rc-community | OS: | Any (Server crashes) |
| Assigned to: | Georgi Kodinov | CPU Architecture: | Any |
[26 Oct 2007 0:36]
Mikhail Serov
[26 Oct 2007 1:16]
Mikhail Serov
1
[26 Oct 2007 3:41]
Valeriy Kravchuk
Thank you for a bug report. Verified just as described. 5.1.21 had the same behaviour, but 5.0.x, indeed, just give error message (as this statement was added in MySQL 5.1.21.)
[30 Oct 2007 15:36]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/36667 ChangeSet@1.2615, 2007-10-30 17:36:09+02:00, gkodinov@magare.gmz +3 -0 Bug #31866: MySQL Server crashes on SHOW CREATE TRIGGER statement SHOW CREATE TRIGGER was not checking for detected errors opening/reading the trigger filer. Fixed to return the already generated error.
[1 Nov 2007 12:42]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/36859 ChangeSet@1.2615, 2007-11-01 14:42:14+02:00, gkodinov@magare.gmz +3 -0 Bug #31866: MySQL Server crashes on SHOW CREATE TRIGGER statement SHOW CREATE TRIGGER was not checking for detected errors opening/reading the trigger file. Fixed to return the already generated error.
[16 Nov 2007 9:34]
Bugs System
Pushed into 5.1.23-rc
[16 Nov 2007 9:36]
Bugs System
Pushed into 6.0.4-alpha
[19 Nov 2007 5:10]
Paul DuBois
Noted in 5.1.23, 6.0.4 changelogs.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.042 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.