Bug #19236 | bad COLUMNS.CHARACTER_MAXIMUM_LENGHT and CHARACTER_OCTET_LENGTH | ||
---|---|---|---|
Submitted: | 21 Apr 2006 0:37 | Modified: | 13 May 2006 4:36 |
Reporter: | Timothy Smith | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Information schema | Severity: | S3 (Non-critical) |
Version: | 5.0.21 | OS: | Any (any) |
Assigned to: | Sergei Glukhov | CPU Architecture: | Any |
[21 Apr 2006 0:37]
Timothy Smith
[25 Apr 2006 8:10]
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/5456
[25 Apr 2006 10:37]
Alexander Barkov
The patch looks ok to push.
[12 May 2006 10:05]
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/6294
[12 May 2006 10:55]
Sergei Glukhov
Fixed in 5.0.22
[13 May 2006 4:36]
Paul DuBois
Noted in 5.0.22 changelog. In the <literal>INFORMATION_SCHEMA.COLUMNS</literal> table, the values for the <literal>CHARACTER_MAXIMUM_LENGTH</literal> and <literal>CHARACTER_OCTET_LENGTH</literal> columns were incorrect for multi-byte character sets.