Bug #35417 | Import of DBDesigner loses insert statements | ||
---|---|---|---|
Submitted: | 18 Mar 2008 20:16 | Modified: | 21 Mar 2008 20:11 |
Reporter: | James Gordon | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S2 (Serious) |
Version: | 5.0.15 RC | OS: | Windows (Vista) |
Assigned to: | Sergei Tkachenko | CPU Architecture: | Any |
[18 Mar 2008 20:16]
James Gordon
[18 Mar 2008 20:17]
James Gordon
Original DBDesigner file.
Attachment: StdSchema.xml (text/xml), 137.14 KiB.
[18 Mar 2008 20:18]
James Gordon
WB file created from DBDesigner file
Attachment: StdSchema.mwb (application/x-zip-compressed, text), 25.25 KiB.
[18 Mar 2008 21:49]
MySQL Verification Team
Thank you for the bug report.
[21 Mar 2008 20:11]
Sergei Tkachenko
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. Currently visual editor requires a set of single row insert statements (as opposed to that MySQL specific multiple row insert syntax). As a temporary workaround all insert statement are rewritten to use common form during import procedure. In future import procedure & visual editor will be changed to store and work with cvs like data set. Actual SQL statements will be generated only during forward engineering applying specifics and provided advantages of target DBMS.