Bug #38196 Import DBD4 xml file MySQL style insert statements imported incorrectly

• Submitted: 17 Jul 2008 13:27
• Modified: 5 Aug 2008 14:40
• Reporter: James Gordon
• Status: Closed
• Category: MySQL Workbench
• Severity: S3 (Non-critical)
• Version: 5.0.23
• OS: Windows (XP)
• Assigned to: Sergei Tkachenko
• CPU Architecture: Any

[17 Jul 2008 13:27] James Gordon

Description:
I have an old DBD4 file that when I convert to WB it incorrectly converts the insert statements.

Converts this...

insert into MemberStatus(idMemberStatus, StatusText) values
(1, 'On Waiting List'),
(2, 'Active'),
(3, 'Inactive');

Converts to this...

INSERT INTO `MemberStatus` (idMemberStatus, StatusText) values
(1, 'On Waiting List'),
(2, 'Active'),
(3, 'Inactive') VALUES (1, 'On Waiting List');
INSERT INTO `MemberStatus` (idMemberStatus, StatusText) values
(1, 'On Waiting List'),
(2, 'Active'),
(3, 'Inactive') VALUES (2, 'Active');
INSERT INTO `MemberStatus` (idMemberStatus, StatusText) values
(1, 'On Waiting List'),
(2, 'Active'),
(3, 'Inactive') VALUES (3, 'Inactive');

I'll attach the DBD4 and WB files later.

How to repeat:
Import DBD4 xml file to WB 5.0.23 and check the MemberStatus table of the attached DBD4 file.

[17 Jul 2008 13:28] James Gordon

DBD4 file

Attachment: BPSchema.xml (text/xml), 96.44 KiB.

[17 Jul 2008 13:29] James Gordon

WB file with the errored insert statements.

Attachment: Errored BPSchema.mwb (application/x-zip-compressed, text), 19.73 KiB.

[19 Jul 2008 12:25] Valeriy Kravchuk

Thank you for a bug report. Verified just as described.

[1 Aug 2008 20:53] Johannes Taxacher

problem is fixed. fix will be in 5.0.24

[5 Aug 2008 14:40] Tony Bedford

An entry was added to the 5.0.24 changelog:

When a DBDesigner 4 XML file was imported into Workbench the INSERT statements were incorrectly converted.