Bug #93772 Changes ... no primary key included in the command.
Submitted: 31 Dec 2018 21:50 Modified: 15 May 16:29
Reporter: Bryce Morrison Email Updates:
Status: Closed Impact on me:
Category:MySQL Workbench: SQL Editor Severity:S7 (Test Cases)
Version:8.0.13 OS:Microsoft Windows (Microsoft Windows 10 Home)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[31 Dec 2018 21:50] Bryce Morrison
I make a bunch of changes in Workbench... and then the list of commands generated does not include the primary key.  This happened with the last version AND with the current version, 8.0.13.

How to repeat:
Change the sort order OR drag a column to the left.  Then make changes. Try to execute the update. View the script that is about to be updated. Scroll to the right, and see that the last part of the script is WHERE ;

Suggested fix:
Make sure that the primary key column is included after the WHERE, but before the ;
[31 Dec 2018 21:53] Bryce Morrison
The attached wb.log file has no record of the problems I am reporting, but I'm attaching it per your request.  The scripts were unable to be executed, as they had no primary key.
[15 May 8:53] Miguel Solorzano
Thank you for the bug report. Please try version 8.0.16, if the issue still happens please attach a screenshot showing the issue. Thanks.
[15 May 16:29] Bryce Morrison
After upgrading to version 8.0.16, the problem did not repeat using the method I described.

More specifically, I did the following:
Made a query.
Edited one value of one of the rows.
Submitted those changes (and the update statement did include the primary key for the first update execution).
Made additional changes without re-running the query.
Submitted those changes.

After that last step, the query to be executed would be displaying incorrectly, missing the primary key.  That problem did not repeat with version 8.0.16, as the primary key was included in the update statement.