Bug #10575 Access Decimal fields won't migrate
Submitted: 12 May 2005 8:49 Modified: 19 May 2005 12:25
Reporter: Richard Black Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Migration Toolkit Severity:S3 (Non-critical)
Version:1.0.5 Beta OS:Microsoft Windows (Windows XP)
Assigned to: CPU Architecture:Any

[12 May 2005 8:49] Richard Black
Description:
Some tables with Decimal fields won't migrate at all, giving me a message saying that Decimal field types can't be migrated.

Others DO get migrated, but the data type appears as (nil) in the Creates.sql script.

This seems to be quite inconsistent - attempting to migrate the same database again told me there were NO mapping problems, where the first time there were around 15 tables (out of 147) which wouldn't migrate because of Decimal fields.

How to repeat:
One of the fields which wouldn't migrate has the following definition:

Field Size: Decimal
Precision: 4
Scale: 0
Decimal Places: Auto
Required: No
Indexed: No

All other properties are blank
[12 May 2005 9:47] Richard Black
Suspect the fix is to map the Access DECIMAL number type to the MySQL DECIMAL type
[12 May 2005 23:38] MySQL Verification Team
I had problems when the scale property is 0.
[19 May 2005 12:25] Michael G. Zinner
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/