Bug #6096 | field.max_length is always zero for numeric columns (stmt_resultset_metadata) | ||
---|---|---|---|
Submitted: | 14 Oct 2004 12:44 | Modified: | 28 Oct 2004 13:10 |
Reporter: | Georg Richter | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 4.1 | OS: | Linux (Linux) |
Assigned to: | Konstantin Osipov | CPU Architecture: | Any |
[14 Oct 2004 12:44]
Georg Richter
[28 Oct 2004 13:10]
Konstantin Osipov
Fixed in 4.1.8 Subject: bk commit - 4.1 tree (konstantin:1.2056) BUG#6096 ChangeSet 1.2056 04/10/27 22:53:50 konstantin@mysql.com +3 -0 A fix and test case for Bug#6096 "field.max_length is always zero for numeric columns (stmt_resultset_metadata)" libmysql/libmysql.c 1.275 04/10/27 22:53:46 konstantin@mysql.com +19 -2 A fix for Bug#6096 "field.max_length is always zero for numeric columns (stmt_resultset_metadata)": set field->max_lenght for numeric columns when we set up skip_result functions. A minor drawback for this approach is that field->max_length can be not zero even if STMT_ATTR_UPDATE_MAX_LENGTH is not set.