MySQL Bugs: #10765: Access DECIMAL fields converted to varchar

Bug #10765	Access DECIMAL fields converted to varchar
Submitted:	20 May 2005 13:32	Modified:	15 Jun 2005 8:41
Reporter:	Richard Black	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Migration Toolkit	Severity:	S2 (Serious)
Version:	1.0.6 Beta	OS:	Windows (Windows XP)
Assigned to:	Michael G. Zinner	CPU Architecture:	Any

Description:
I assume this is related to the fix for bug #10575, but when I try to migrate Decimal fields from Access to MySQL, it converts them to varchar instead of decimal.

This might be usable, except that the varchar isn't even large enough to hold the decimal value. For example, a Decimal (18,2) field was converted to varchar(18) - which COULD hold all the digits, but NOT the decimal point.

As I said on #10575, shouldn't this convert to a DECIMAL data type?

This seems to be the case on EVERY Decimal field

How to repeat:
Try to migrate a table with Decimal fields from Access to MySQL

Suggested fix:
Migrate from Access DECIMAL field type to MySQL DECIMAL field type

Thank you for the bug report, below the script created:
-- ----------------------------------------------------------------------
-- SQL create script
-- ----------------------------------------------------------------------

DROP DATABASE IF EXISTS `db1`;

CREATE DATABASE `db1`
  CHARACTER SET latin1 COLLATE latin1_swedish_ci;

CREATE TABLE `db1`.`Table1` (
  `as` VARCHAR(18) NULL,
  `sd` VARCHAR(50) NULL
)
ENGINE = INNODB;

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