Re: Migration Errors - Solution

[Garrett Williams]

The functional solution within the Migration Toolkit is to specify the proper character set.

This can be done at the Schema Creation step of the migration.
In the database tree, select the table where the error occurred.
Click advanced and it shows the sql for creating the table.
The column where the error occurred is probably like this:

DROP TABLE IF EXISTS `mydb`.`mytable`;
CREATE TABLE `mydb`.`mytable` (
`PKID` INT(10) NOT NULL AUTO_INCREMENT,
... ,
`notes_field` VARCHAR(255) NULL,
... ,
PRIMARY KEY (`PKID`)
)
ENGINE = INNODB;

Add 'CHARACTER SET utf8 COLLATE utf8_general_ci' to specify the character type which can handle characters like # sign, etc., like this:

DROP TABLE IF EXISTS `mydb`.`mytable`;
CREATE TABLE `mydb`.`mytable` (
`PKID` INT(10) NOT NULL AUTO_INCREMENT,
...
`notes_field` VARCHAR(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL,
...
PRIMARY KEY (`PKID`)
)
ENGINE = INNODB;

Then the migration does not error out. This worked for me.



Edited 1 time(s). Last edit at 01/10/2008 12:34PM by Garrett Bach.