Description:
When trying to migrate an Access Database to MySQL, the MySQL Migration Toolkit automatically want to convert the BOOLEAN Fields in Access to TINYINT(1) Fields in MySQL. When you change during the "Schema Creation" process the TINYINT(1)fields to BOOLEAN, apply the changes and recreate the objects, it looks like MySQL would do it all right, because the changes fields should be created with Boolean type. But after creating the database, the fields are from the wrong datatype TINYINT(1)! And what is even worse - you can not easily change this datatype in MySQL Administrator to BOOLEAN, because "-1" is not BOOLEAN!
And an other big problem with that - Visual Basic can not work with that data type!
How to repeat:
- convert an Access with an table with a Boolean datatype field to a MySQL Database
- during schema creation process, show all objects
- change the datatype from TINYINT(1) to BOOLEAN
- "Apply changes", "Recreate Objects"
- Check the changes - they look all right
- Convert the database
- Check with Database Administrator the datatypes of the changed field
- it is again TINYINT(1) and not the desired BOOLEAN
Suggested fix:
Preferred fix: - do not use TINYINT(1) as Standard conversion datatype for BOOLEAN, keep the ACCESS datatype BOOLEAN for the process in MySQL
subordinate fix: - keep the applied changes during schema creation for the later migration process, so that the fields are BOOLEAN and not TINYINT(1)!
