Bug #109052 WorkBench doesn't log SQL actions applied on the result grid
Submitted: 10 Nov 2022 11:04 Modified: 28 Feb 2023 21:03
Reporter: Richard Bostock Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0.23 OS:Windows (Microsoft Windows 10 Home)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[10 Nov 2022 11:04] Richard Bostock 
Description:
Run a query to view a table
Change a cell in the Result Grid - e.g. Set to NULL
Click on Apply
Confirm the change
Review the logs - no log contains the run SQL action

How to repeat:
SQL actions will not be logged on any change from the Results Grid

Suggested fix:
Add the SQL action to the sql_actions_<USER> log file.
[28 Feb 2023 12:01] MySQL Verification Team 
Hello Richard,

Thank you for the bug report.
Launch workbench under debug mode (--log-level=debug3, more details about log are explained here - https://dev.mysql.com/doc/workbench/en/workbench-reporting-bugs.html) and you can see SQL actions done on Results Grid here C:\Users\[user]\AppData\Roaming\MySQL\Workbench\sql_history\[latest file]. Thanks.

Regards,
Ashwini Patil
[28 Feb 2023 21:03] Richard Bostock 
Many thanks - the sql_history was what I was looking for. 

Ideally this would be clearer in the folder structure (I'd expected this to be in the log directory) or possibly with a file extension that indicates that these are log files. However, many thanks for providing the information as this is very useful.