Bug #72155 Table editor no longer honors "Confirm data changes"
Submitted: 28 Mar 2014 23:38 Modified: 14 May 2014 22:26
Reporter: Byron Palmer Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S2 (Serious)
Version:6.1.4 OS:Windows (Microsoft Windows 7 Service Pack 1 (build 7601), 64-bit)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[28 Mar 2014 23:38] Byron Palmer
Description:
I use this feature to get changes I need so I can apply them in a controlled migration of the database. It was easy and very nice, and now it doesn't do that I can no longer get the SQL that is being executed.

Please return it.

How to repeat:
Select from a table.

Edit the data.

Hit Apply.

No query as to whether one wants to execute the sql, and no sql of what was going to be executed.
[29 Mar 2014 3:03] MySQL Verification Team
Thank you for the bug report.
[31 Mar 2014 16:37] Byron Palmer
Tested it with the new 6.1.4 and problem is still the same. Not that I expected it to be fixed that quickly.
[31 Mar 2014 23:53] Yoshiaki Yamasaki
Hi Godofredo,

Thank you for the information. I checked http://bugs.mysql.com/bug.php?id=72155.

I think this feature is used by many people. Therefore, I hope that this problem will fix quickly.
[2 Apr 2014 1:57] Yoshiaki Yamasaki
I'm sorry, I made a mistake in last post.

I thought this report is "http://bugs.mysql.com/bug.php?id=72169".
[2 Apr 2014 3:05] Mark Aldridge
I just upgraded from MySQL Workbench 5.2.47 up to 6.1.  I use the confirm feature on a regular basis to view SQL query code and to view detailed information on errors.  Currently, the small output window simply states "1 error(s) saving changes to table XYZ" when there is an error.  This does not give me anything to go on when troubleshooting.

Please fix!  Thanks in advance.
[6 Apr 2014 21:35] MySQL Verification Team
http://bugs.mysql.com/bug.php?id=72254 duplicate of this one.
[7 Apr 2014 8:39] Mike Lischke
Bug #72169 was marked as duplicate of this report
[14 May 2014 22:26] Philip Olson
Fixed as of the upcoming MySQL Workbench 6.1.6 release, and here's the changelog entry:

After clicking "Apply" to save changes to a result set in the SQL editor,
the executed SQL statement was no longer being displayed.

Thank you for the bug report.