Bug #33649 | Is multi-byte encoding applied twice, leading to squared size ? | ||
---|---|---|---|
Submitted: | 3 Jan 2008 12:35 | Modified: | 13 Nov 2008 3:19 |
Reporter: | Joerg Bruehe | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Charsets | Severity: | S2 (Serious) |
Version: | 6.0.4-alpha | OS: | Any |
Assigned to: | Sergei Glukhov | CPU Architecture: | Any |
[3 Jan 2008 12:35]
Joerg Bruehe
[8 Oct 2008 11:09]
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/55723 2859 Sergey Glukhov 2008-10-08 Bug#33649 Is multi-byte encoding applied twice, leading to squared size ? Some columns are declared in a wrong way, which results in this double length multiplication. The correct character length should be 64, and the correct octet length should be 256. The fix is to use NAME_CHAR_LEN instead of NAME_LEN
[8 Oct 2008 11:24]
Alexander Barkov
The patch http://lists.mysql.com/commits/55723 is ok to push.
[9 Oct 2008 10:18]
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/55903 2862 Sergey Glukhov 2008-10-09 Bug#33649 Is multi-byte encoding applied twice, leading to squared size ? Some columns are declared in a wrong way, which results in this double length multiplication. The correct character length should be 64, and the correct octet length should be 256. The fix is to use NAME_CHAR_LEN instead of NAME_LEN
[10 Nov 2008 10:52]
Bugs System
Pushed into 6.0.8-alpha (revid:sergey.glukhov@sun.com-20081009101746-5cnojb55yibo2wpp) (version source revid:sergey.glukhov@sun.com-20081009101746-5cnojb55yibo2wpp) (pib:5)
[13 Nov 2008 3:19]
Paul DuBois
Noted in 6.0.9 changelog. The ROUTINES.DATA_TYPE, REFERENTIAL_CONSTRAINTS.SPECIFIC_SCHEMA, REFERENTIAL_CONSTRAINTS.SPECIFIC_NAME, REFERENTIAL_CONSTRAINTS.PARAMETER_NAME, REFERENTIAL_CONSTRAINTS.DATA_TYPE columns were declared longer than the maximum allowed identifier length.