| Bug #3645 | PROCEDURE ANALYSE() recommends illegal FLOAT columns | ||
|---|---|---|---|
| Submitted: | 4 May 2004 8:39 | Modified: | 7 Sep 2004 8:40 |
| Reporter: | Hans-Peter Grimm | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 4.0.x | OS: | any? |
| Assigned to: | Jani Tolonen | CPU Architecture: | Any |
[7 Sep 2004 8:40]
Jani Tolonen
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.
If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information
about accessing the source trees is available at
http://www.mysql.com/doc/en/Installing_source_tree.html
Description: PROCEDURE ANALYSE() recommends FLOAT columns with a negative display width and 1 decimal for DOUBLE columns. Tested on Solaris 9 (4.0.15) and Win2k (4.0.17). How to repeat: mysql> create table test.foo (d double); Query OK, 0 rows affected (0.01 sec) mysql> insert into test.foo select rand(); Query OK, 1 row affected (0.00 sec) Records: 1 Duplicates: 0 Warnings: 0 mysql> select * from test.foo procedure analyse(1,1); *************************** 1. row *************************** Field_name: foo.d Min_value: 0.83120087425336 Max_value: 0.83120087425336 Min_length: 8 Max_length: 8 Empties_or_zeros: 0 Nulls: 0 Avg_value_or_avg_length: 0.83120087425336 Std: 0 Optimal_fieldtype: FLOAT(-24,1) NOT NULL 1 row in set (0.00 sec)