Bug #56710 | Varchar User Defined Type bug at forward engineer of insert row | ||
---|---|---|---|
Submitted: | 10 Sep 2010 7:12 | Modified: | 29 Sep 2010 14:56 |
Reporter: | Dimitri Pacini | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
Version: | 5.2.27 CE | OS: | Windows (7) |
Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
Tags: | Varchar User Defined Type Forward Engineer |
[10 Sep 2010 7:12]
Dimitri Pacini
[10 Sep 2010 7:41]
Valeriy Kravchuk
Thank you for the bug report. Verified on Windows XP.
[29 Sep 2010 10:32]
Johannes Taxacher
fix confirmed in repository
[29 Sep 2010 14:56]
Tony Bedford
An entry has been added to the 5.2.29 changelog: If a table containing a User Defined Type based on VARCHAR was forward engineered, the resulting SQL did not correctly quote the VARCHAR value, resulting in a server error. For example, the following code was generated: CREATE TABLE IF NOT EXISTS `x`.`tabley` (`customstring` VARCHAR(10)); INSERT INTO `x`.`tabley` (`id_customstring`) VALUES (example); The correct INSERT statement should be: INSERT INTO `x`.`tabley` (`id_customstring`) VALUES ('example');