Bug #74140 | New Version 6.2.3.12313 generated sometimes wrong UPDATE Queries... | ||
---|---|---|---|
Submitted: | 29 Sep 2014 15:42 | Modified: | 5 Nov 2014 2:23 |
Reporter: | Martin Seysen | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 6.2.3.12313 | OS: | MacOS |
Assigned to: | CPU Architecture: | Any | |
Tags: | generated, GUI, regression, workbench |
[29 Sep 2014 15:42]
Martin Seysen
[29 Sep 2014 16:49]
MySQL Verification Team
Thank you for the bug report. Please provide a dump file with insert data so is possible to run the queries. Thanks.
[30 Sep 2014 8:06]
Martin Seysen
dump file with some data (INSERTs)
Attachment: dump.sql (text/x-sql), 2.50 KiB.
[30 Sep 2014 10:00]
MySQL Verification Team
Thank you for the test case. I see 2 different query set with 6.2.3 and 6.1.7 for the same update. // 6.2.3 UPDATE `test`.`table` SET `dstamp`='1111' WHERE `uid`='0'; // 6.1.7 UPDATE `test`.`table` SET `dstamp`='1111' WHERE `id`='2' and`uid`='0' and`dstamp`='0'; Thanks, Umesh
[5 Nov 2014 2:23]
Philip Olson
Posted by developer: Fixed as of the upcoming MySQL Workbench 6.2.4 release, and here's the changelog entry: MySQL Workbench generated incorrect UPDATE queries for tables without a Primary Key even where unique keys were present. Thank you for the bug report.