Bug #14135 NVARCHAR column is translated to VARCHAR, but not to VARCHAR UNICODE

• Submitted: 19 Oct 2005 9:28
• Modified: 19 Oct 2005 13:06
• Reporter: Victoria Reznichenko
• Status: Closed
• Category: MySQL Migration Toolkit
• Severity: S3 (Non-critical)
• OS: Linux (linux)
• CPU Architecture: Any

[19 Oct 2005 9:28] Victoria Reznichenko

Description:
During migration from MS SQL to MySQL, MySQL Migration Toolkit converts NVARCHAR COLUMN to VARCHAR with latin1 character set, but not to VARCHAR with unicode character set.

How to repeat:
1. Create table on MS SQL with NVARCHAR column.
2. Migrate table from MS SQL to MySQL
3. Check the result.

[19 Oct 2005 13:06] 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

Additional info:

A table like

CREATE TABLE [dbo].[product] (
	[idproduct_group] [int] NOT NULL ,
	[idproduct] [int] NOT NULL ,
	[name] [nchar] (20) COLLATE Latin1_General_CI_AS NULL ,
	[description] [nvarchar] (50) COLLATE Latin1_General_CI_AS NULL 
) ON [PRIMARY]
GO

is now migrated to

CREATE TABLE `Northwind_dbo`.`product` (
  `idproduct_group` INT(10) NOT NULL,
  `idproduct` INT(10) NOT NULL,
  `name` CHAR(20) CHARACTER SET utf8 COLLATE utf8_general_ci NULL,
  `description` VARCHAR(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL,
  PRIMARY KEY (`idproduct_group`, `idproduct`)
)
ENGINE = INNODB;