Bug #39186 Crash in String::append when inserting duplicate empty strings an uft8 SET col
| Submitted: | 2 Sep 2008 13:49 | Modified: | 18 Oct 2008 15:56 |
|---|---|---|---|
| Reporter: | Davi Arnaut (OCA) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 6.0 | OS: | Any |
| Assigned to: | Georgi Kodinov | CPU Architecture: | Any |
| Tags: | regression | ||
[2 Sep 2008 13:49]
Davi Arnaut
[8 Sep 2008 14:55]
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/53534 2692 Georgi Kodinov 2008-09-08 Bug #39186: Crash in String::append when inserting duplicate empty strings an uft8 SET col Fixed a problem in constructing a string representation of a ENUM field when reporting key duplicate error. Note : no test case as the one for bug #38701 covers this one as well.
[9 Sep 2008 12:39]
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/53604 2692 Georgi Kodinov 2008-09-08 Bug #39186: Crash in String::append when inserting duplicate empty strings an uft8 SET col Fixed a problem in constructing a string representation of a ENUM field when reporting key duplicate error. Note : no test case as the one for bug #38701 covers this one as well.
[17 Oct 2008 16:41]
Bugs System
Pushed into 6.0.8-alpha (revid:kgeorge@mysql.com-20080908145416-wvmvl4aigvthra71) (version source revid:kpettersson@mysql.com-20080911114255-81pt7q1uvl1fkojq) (pib:5)
[18 Oct 2008 15:56]
Paul DuBois
Noted in 6.0.8 changelog. The server could crash when attempting to insert duplicate empty strings into a utf8 SET column.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.063 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.