Bug #24669 Field Name Conversion
Submitted: 28 Nov 2006 19:11 Modified: 4 Jan 2007 0:19
Reporter: Thomas Roethling Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Migration Toolkit Severity:S3 (Non-critical)
Version:1.1.6rc OS:Windows (windows)
Assigned to: CPU Architecture:Any

[28 Nov 2006 19:11] Thomas Roethling
Description:
when converting the database i have a field that is called:

item_price/carat

but afetr the conversion it is called under mysql:

item_price_carat

it did convert it porperly in a previous version!

Best regards!

Thomas

How to repeat:
try to convert a access database with the field name as described
[28 Nov 2006 22:31] MySQL Verification Team
Thank you for the bug report.

-- ----------------------------------------------------------------------
-- MySQL Migration Toolkit
-- SQL Create Script
-- ----------------------------------------------------------------------

SET FOREIGN_KEY_CHECKS = 0;

CREATE DATABASE IF NOT EXISTS `testbug`
  CHARACTER SET latin1 COLLATE latin1_swedish_ci;
USE `testbug`;
-- -------------------------------------
-- Tables

DROP TABLE IF EXISTS `testbug`.`tbj`;
CREATE TABLE `testbug`.`tbj` (
  `id` INT(10) NOT NULL AUTO_INCREMENT,
  `item_price_carat` DOUBLE(15, 5) NULL,
  PRIMARY KEY (`id`),
  INDEX `id` (`id`)
)
ENGINE = INNODB;

SET FOREIGN_KEY_CHECKS = 1;

-- ----------------------------------------------------------------------
-- EOF
[4 Dec 2006 0:19] Michael G. Zinner
This new behavior is actually a bug fix. Please see this bug report for details.

http://bugs.mysql.com/bug.php?id=24379

Why is this causing problems for you? Is there a workaround?

If I change it back other customers will have problems again.
[5 Jan 2007 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".