| Bug #133 | Procedure analyse displays NEWDATE type whereas it doesn't exist | ||
|---|---|---|---|
| Submitted: | 7 Mar 2003 13:49 | Modified: | 12 Mar 2003 6:41 |
| Reporter: | jocelyn fournier (Silver Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: MyISAM storage engine | Severity: | S3 (Non-critical) |
| Version: | 4.x | OS: | Any (all) |
| Assigned to: | Michael Widenius | CPU Architecture: | Any |
[12 Mar 2003 6:41]
Michael Widenius
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at http://www.mysql.com/downloads/ Fixed in 3.23.57 and 4.0.12

Description: On a table with defined with a DATE type, PROCEDURE ANALYSE displays : | inscrit.dateinscr | 1876-01-23 | 2003-03-07 | 10 | 10 | 0 | 0 | 10.0000 | NULL | NEWDATE NOT NULL | How to repeat: Run PROCEDURE ANALYSE() on a table with a date column. Suggested fix: In MySQL 4.0 : line 680 in sql_analyce.cc, replace ans.append("NEWDATE", 7); by ans.append("DATE", 4); In MySQL 4.1, same thing with line 669