Bug #93772 | Changes ... no primary key included in the command. | ||
---|---|---|---|
Submitted: | 31 Dec 2018 21:50 | Modified: | 15 May 2019 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: | Windows (Microsoft Windows 10 Home) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[31 Dec 2018 21:50]
Bryce Morrison
[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 2019 8:53]
MySQL Verification Team
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 2019 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.