Bug #24810 Migration ToolKit to Access (Boolean Field)
Submitted: 5 Dec 2006 1:47 Modified: 15 Jan 2007 17:46
Reporter: Pemt Oper Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Migration Toolkit Severity:S3 (Non-critical)
Version:1.1.6 OS:Windows (Windows)
Assigned to: CPU Architecture:Any

[5 Dec 2006 1:47] Pemt Oper
Description:
The new version of Migration toolkit ist converting to TIny unsigned and the
true/flase (bollena field) are converted to -1 and 1.

we have to use the old/old version to convert boolean and get result 1 and 0

How to repeat:
Just Migrate any MSaccess to MySQL with Boolean Field
[5 Dec 2006 3:45] Pemt Oper
The new version of Migration toolkit is converting to TIny unsigned and the
true/false (boolean field) are converted to 1 and -1.

we have to use the old/old version (1.0.25) to convert boolean and get result 1 and 0
[5 Dec 2006 9:45] Valeriy Kravchuk
Thank you for a problem report. What exact "new" version are you talking about? 1.1.6?
[5 Dec 2006 12:46] Pemt Oper
We tested with 5.0 r1+ till latest stil same behavior conversion are tiny unsigned and true/false are converted 1/-1.

look like this isue doesnt appear in 1.0.25
[5 Dec 2006 13:05] MySQL Verification Team
Thank you for the bug report.

mysql> select * from table1;
+----+-------+
| id | col2  |
+----+-------+
|  0 | false |
| -1 | true  |
+----+-------+
2 rows in set (0.00 sec)

mysql> show create table table1\G
*************************** 1. row ***************************
       Table: table1
Create Table: CREATE TABLE `table1` (
  `id` tinyint(1) NOT NULL,
  `col2` varchar(50) default NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1
1 row in set (0.00 sec)

mysql>
[15 Jan 2007 17:46] Michael G. Zinner
This was actually a fix of an previous bug. In MS Access TRUE stands for -1. This is now migrated as expected. This change was needed to allow MS Access applications to work with migrated databases and linked tables.

1 for TRUE caused the MS Access application to fail.
[2 Feb 2007 6:19] Simon Litchfield
Perhaps we should provide a new parameter under the 'Object Mapping' step - 'Migration of type table' - User defined. Something like convertAccessBooleans=yes|no, defaulting to no.

That would be nice, since many Access ported applications test for TRUE|FALSE keywords instead of -1|0 anyway.
[24 May 2007 13:48] MySQL Verification Team
Bug http://bugs.mysql.com/bug.php?id=28643 was marked as duplicate of
this one.