Bug #14207 | strange change of values CHARACTER_OCTET_LENGTH and CHARACTER_MAXIMUM_LENGTH | ||
---|---|---|---|
Submitted: | 21 Oct 2005 11:53 | Modified: | 27 Oct 2005 2:43 |
Reporter: | Carsten Segieth | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.0.16-bk | OS: | Linux (Linux) |
Assigned to: | Ramil Kalimullin | CPU Architecture: | Any |
[21 Oct 2005 11:53]
Carsten Segieth
[24 Oct 2005 9:21]
Sergei Golubchik
Citing the standard: 3) The values of DATA_TYPE, CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_LENGTH, CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA, CHARACTER_SET_NAME, COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_NAME, NUMERIC_PRECISION, NUMERIC_PRECISION_RADIX, NUMERIC_SCALE, DATETIME_PRECISION, USER_DEFINED_TYPE_CATALOG, USER_DEFINED_TYPE_SCHEMA, USER_DEFINED_TYPE_NAME, SCOPE_CATALOG, SCOPE_SCHEMA, and SCOPE_NAME are, respectively, the data type, the maximum length in characters if it is a character string type, the maximum length in octets if it is a character string type <...>
[24 Oct 2005 11:47]
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/internals/31376
[25 Oct 2005 11:53]
Ramil Kalimullin
fixed in 5.0.16
[27 Oct 2005 2:43]
Paul DuBois
Noted in 5.0.16 changelog.