Bug #10053 | MS Float fields defined as type (nil) in destination table | ||
---|---|---|---|
Submitted: | 21 Apr 2005 9:07 | Modified: | 17 May 2005 8:26 |
Reporter: | Peter Whitefield | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Migration Toolkit | Severity: | S1 (Critical) |
Version: | 1.0.4 alpha | OS: | Windows (windows xp) |
Assigned to: | Michael G. Zinner | CPU Architecture: | Any |
[21 Apr 2005 9:07]
Peter Whitefield
[21 Apr 2005 9:25]
Peter Whitefield
Apologies, I think this is a duplicate because the MS field type is actually a double (I'd exported the access table as .txt and found 'Col13=Mileage Float' in the scheme.ini file created by the access export) Having just discovered how to look at the table definitions in access the field Mileage is actually a double.
[21 Apr 2005 11:32]
Peter Whitefield
Looking through the 12 tables that failed to migrate this problem has occurred when the access data type is Number and the field size is either Double or Byte (I believe that the number of decimal places is set to Auto in access in all cases).
[17 May 2005 8:26]
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 bugfix, yourself. More information about accessing the source trees is available at http://www.mysql.com/doc/en/Installing_source_tree.html