Bug #54272 | Forward Engineer generates SQL statements with redundant carriage returns. | ||
---|---|---|---|
Submitted: | 7 Jun 2010 3:04 | Modified: | 29 Jun 2010 9:21 |
Reporter: | Yen-Wei Liu | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 5.2.22 | OS: | Windows (XP SP3) |
Assigned to: | Alexander Musienko | CPU Architecture: | Any |
[7 Jun 2010 3:04]
Yen-Wei Liu
[7 Jun 2010 4:33]
Yen-Wei Liu
As for scenario 2, please ignore it. After reviewing the data, I found out it's not the issue of Forward Engineer. After importing from a SQL file, these DDL statements with Views or Triggers are appended extra carriage-return characters, before Forward Engineering. This is another issue I will look into.
[22 Jun 2010 15:19]
Mike Lischke
fix confirmed in repository
[29 Jun 2010 9:22]
Tony Bedford
An entry has been added to the 5.2.25 changelog: When forward engineering to a live database, the generated SQL statements contained an erroneous additional carriage return (^M) at the end of each line. However, this manifested in two ways. In the first case, in the Forward Engineer to Database wizard, if Save to File was selected, a carriage-return character was appended to each line. In the second case, if Copy to Clipboard was selected, and the content subsequently pasted from the clipboard to an editor, then the extra carriage return characters was attached only to the DDL statements inside Create View and Create Trigger.