| Bug #10716 | Procedure Analyse results in wrong values for optimal field type | ||
|---|---|---|---|
| Submitted: | 18 May 2005 15:42 | Modified: | 6 Jan 2006 5:32 |
| Reporter: | Johann-Peter Hartmann | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 4.0.16-5.0.3 | OS: | Windows (Windows, Linux) |
| Assigned to: | Jani Tolonen | CPU Architecture: | Any |
[18 May 2005 16:42]
MySQL Verification Team
Thank you for the bug report.
[9 Sep 2005 10:08]
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/29556
[9 Sep 2005 14:27]
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/29568
[6 Jan 2006 5:32]
Paul DuBois
Noted in 4.1.16 changelog.
Description: Dear MySQL team, seems like there is still one bug left in procedure analyse. It is similar to 3645, but still does exist. Best Regards, Johann How to repeat: CREATE TABLE bla (bla DOUBLE NOT NULL ); INSERT INTO bla ( bla )VALUES ('100000'); SELECT * FROM bla PROCEDURE ANALYSE ( 1, 1 );