Bug #21034 Mysql 4.1 -> MySQL 5.1: FLOAT becomes FLOAT(0,0)
Submitted: 13 Jul 2006 13:39 Modified: 8 Aug 2006 15:35
Reporter: Roland Bouman Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Migration Toolkit Severity:S3 (Non-critical)
Version:1.1.1 beta OS:
Assigned to: CPU Architecture:Any
Tags: FLOAT, Migration Toolkit, MySQL

[13 Jul 2006 13:39] Roland Bouman 
Description:
In a MySQL 4.1 to MySQL 5.1 (4.1.20 to 5.1.11) setup, the Migration toolkit maps FLOAT columns in the source to FLOAT(0,0) column in the target. 

FLOAT (0,0) is not a valid datatype, and the migration fails for these objects

How to repeat:
Migrate this source;

CREATE TABLE t (
    col FLOAT
)

Suggested fix:
Ahem...don't generate FLOAT(0,0) columns
[14 Jul 2006 12:41] MySQL Verification Team 
Thank you for the bug report.

DROP TABLE IF EXISTS `db78`.`t`;
CREATE TABLE `db78`.`t` (
  `col` FLOAT(0, 0) NULL
)
ENGINE = INNODB;
[8 Aug 2006 15:35] Michael G. Zinner 
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 bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html