Bug #41290 Database Synchronisation of datatype double failure
Submitted: 8 Dec 2008 9:16 Modified: 6 Aug 2009 16:00
Reporter: Lars Monecke Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.0.29 SE OS:Windows (XP 64)
Assigned to: Alexander Musienko CPU Architecture:Any
Tags: CHECKED

[8 Dec 2008 9:16] Lars Monecke 
Description:
Synchronisation of attached test.mwb failes to MySQL Server 5.0.x  because of "DOUBLE(265)"
send as datatype for "double_value":

CREATE  TABLE IF NOT EXISTS `mydb`.`foobar` (
  `foobar_id` INT(11) NOT NULL AUTO_INCREMENT ,
  `double_value` DOUBLE(256) NULL DEFAULT NULL ,
  `boolean_value` BOOLEAN NULL DEFAULT NULL ,
  PRIMARY KEY (`foobar_id`) )
ENGINE = InnoDB
DEFAULT CHARACTER SET = latin1
COLLATE = latin1_swedish_ci;

similiar to: http://bugs.mysql.com/bug.php?id=39257

How to repeat:
do a Database Synchronisation with attached mwb file

Suggested fix:
use "DOUBLE" only
[8 Dec 2008 9:17] Lars Monecke 
test mwb file

Attachment: test20081208.mwb (application/octet-stream, text), 3.24 KiB.
[8 Dec 2008 14:05] MySQL Verification Team 
Thank you for the bug report. Could you please try latest release 5.0.28. Thanks in advance.
[9 Jan 2009 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".
[12 Jan 2009 8:32] Lars Monecke 
Same with 5.0.29 SE
[13 Jan 2009 17:52] Susanne Ebrecht 
Verified as described by using Workbench 5.0.29 SE.
[5 Aug 2009 10:25] Johannes Taxacher 
DOUBLE is now exported as entered by user.
fix will be in 5.1.17
[6 Aug 2009 16:00] Tony Bedford 
An entry was added to the 5.1.17 changelog:

A model failed to synchronize with a live database, as a column of type DOUBLE was exported as a type DOUBLE(256).