Bug #44464 Workbench SE Synch with collation difference fails
Submitted: 24 Apr 2009 18:05 Modified: 15 Jun 2009 10:34
Reporter: Marc Ford Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:5.0.30 OS:Windows
Assigned to: CPU Architecture:Any
Tags: collation, latin1_swedish_ci, ROW_FORMAT

[24 Apr 2009 18:05] Marc Ford
Description:
With all fields, tables, and database default collations set to utf8_general_ci, a Schema Synch to mySQL Database left fields with latin1_swedish_ci.

Having changed 2 tables (and their fields) collation to utf8_general_ci in the actual database, a subsequent Workbench Schema synch failed with errors because the ROW_FORMAT statement was blank.  Removing the ROW_FORMAT statements resulted in a successful synch.

==========================
Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 6

ALTER TABLE `controldb01`.`cc_rom` 
  ADD CONSTRAINT `fk_cc_rom_cc_list_values3`
  FOREIGN KEY (`sw_type` )
  REFERENCES `controldb01`.`cc_list_values` (`id_list_values` )
  ON DELETE NO ACTION
  ON UPDATE NO ACTION, ROW_FORMAT =  
Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 11

ALTER TABLE `controldb01`.`cc_rom_cals` 
  ADD CONSTRAINT `fk_cc_rom_cals_cc_functions`
  FOREIGN KEY (`id_functions` )
  REFERENCES `controldb01`.`cc_functions` (`id_functions` )
  ON DELETE NO ACTION
  ON UPDATE NO ACTION, 
  ADD CONSTRAINT `fk_cc_rom_cals_cc_rom_cals_comment`
  FOREIGN KEY (`id_cal_comment` )
  REFERENCES `controldb01`.`cc_rom_cals_comment` (`id_cal_comment` )
  ON DELETE NO ACTION
  ON UPDATE NO ACTION, ROW_FORMAT =  
SQL script execution finished: statements: 43 succeeded, 2 failed
=====================

The executed code was...
ALTER TABLE `controldb01`.`cc_rom` DROP FOREIGN KEY `fk_cc_rom_cc_list_values3` ;

ALTER TABLE `controldb01`.`cc_rom` 
  ADD CONSTRAINT `fk_cc_rom_cc_list_values3`
  FOREIGN KEY (`sw_type` )
  REFERENCES `controldb01`.`cc_list_values` (`id_list_values` )
  ON DELETE NO ACTION
  ON UPDATE NO ACTION, ROW_FORMAT =  ;

ALTER TABLE `controldb01`.`cc_rom_cals` DROP FOREIGN KEY `fk_cc_rom_cals_cc_functions` , DROP FOREIGN KEY `fk_cc_rom_cals_cc_rom_cals_comment` ;

ALTER TABLE `controldb01`.`cc_rom_cals` 
  ADD CONSTRAINT `fk_cc_rom_cals_cc_functions`
  FOREIGN KEY (`id_functions` )
  REFERENCES `controldb01`.`cc_functions` (`id_functions` )
  ON DELETE NO ACTION
  ON UPDATE NO ACTION, 
  ADD CONSTRAINT `fk_cc_rom_cals_cc_rom_cals_comment`
  FOREIGN KEY (`id_cal_comment` )
  REFERENCES `controldb01`.`cc_rom_cals_comment` (`id_cal_comment` )
  ON DELETE NO ACTION
  ON UPDATE NO ACTION, ROW_FORMAT =  ;

 

How to repeat:
?
[15 May 2009 10:34] Susanne Ebrecht
Many thanks for writing a bug report.

Unfortunately, I can't follow you. Please give us a step by step description what you did and how you recognised that the charset settings are wrong.
[15 Jun 2009 23: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".